After fence event on one node resources were relocated to another node, but after a reboot pacemaker tried to fail back the resources back to original owner
Issue
-
After fence event on one node3, the resources RG_APPS, RG_DB, RG_REPDB which were previously running on node3 were getting relocated to other nodes as per location constraints. But after a reboot of failed node pacemaker tried to fail back the resources back to original owner even if there were resource constraints configured to not to fail back a resource:
$ pcs config [...] Location Constraints: Resource: RG_APPS Enabled on: node1 (score:50) (id:location-RG_APPS-node1-50) Enabled on: node3 (score:50) (id:location-RG_APPS-node3-50) Enabled on: node1 (score:INFINITY) (role: Started) (id:cli-prefer-RG_APPS) Disabled on: node2 (score:-INFINITY) (id:location-RG_APPS-node2--INFINITY) Resource: RG_DB Enabled on: node3 (score:50) (id:location-RG_DB-node3-50) Enabled on: node2 (score:50) (id:location-RG_DB-node2-50) Disabled on: node1 (score:-INFINITY) (id:location-RG_DB-node1--INFINITY) Resource: RG_REPDB Enabled on: node3 (score:100) (id:location-RG_REPDB-node3-100) Enabled on: node1 (score:10) (id:location-RG_REPDB-node1-10) Enabled on: node2 (score:10) (id:location-RG_REPDB-node2-10) Ordering Constraints: Colocation Constraints: [...]
Environment
- Red Hat Enterprise Linux 7.1 with High Availability Add-Ons
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
