Why does clustered service starts on wrong/non-preferred node?
Issue
- When clustered services are started from either Luci or the command line the services do not start on the highest priority node within the failover domain.
- Even though the clustered service is configured in an ordered failover domain it is not starting on the highest priorty node
Environment
- Red Hat Enterprise Linux 5
- Red Hat Enterprise Linux 6
- Red Hat Cluster Suite
- Red Hat High Availability Add On
- Clustered service configured configured to run in an ordered-restricted failover domain with nofailback="1"
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
