'pcs resource move' prevents a resource from failing back to its original node later in a RHEL 6 or 7 High Availability cluster with pacemaker
Issue
- After using
pcs resource move, a resource will not failback to its original location if it eventually fails or the node its running on fails. pcs resource moveseems to ban the node its running on.pcs resource move resource-idcommand prevents the resource from moving back on the cluster node. For example, when a resource is moved from cluster node1 to node2 manually, then the resource fails to start on node1 when it is failed over again from node2. The resource is seen in the stopped state on node1.- Red Hat Cluster created a contraint with score of -INFINITY when I tried to move services
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
pacemaker
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.
