`pcs status` doesn't display why certain resource is in stopped state
Issue
In general pacemaker resource can be stopped for various reasons i.e. manually stopped, failed to start, failed during normal operation, has nowhere to run due to constraint restriction (allowed node is down etc.).
Is pacemaker able to track the reason why resource is stopped? i.e. display it in pcs status?
Is there possibility to not display resources which are in stopped state because they have currently nowhere to run due to constraint limitations?
Environment
- Red Hat Enterprise Linux 7
- pacemaker cluster
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.