Why `exportfs` cluster resource fails to monitor after successful start when exported path contains symlink?
Issue
Trying to export path that contains symlink using exportfs resource agent results in successful 'start' operation, but immediately fails on first 'monitor' operation with exit code 7 - not running.
Environment
- Red Hat Enterprise Linux 7 with High-Availability or Resilient Storage Add-on
exportfsresource agent
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.