Issues with pacemaker-1.1.16-12.el7_4.4.x86_64 for guest nodes (virtual remote nodes)
Issue
On pacemaker-1.1.16-12.el7_4.4 our location constraints are no longer working as they were before in previous versions of pacemaker.
vg1A (ocf::heartbeat:LVM): FAILED[ circle2.example.com ]
Failed Actions:
* vg1A_monitor_0 on circle2.example.com 'unknown error' (1): call=466, status=complete, exit reason='LVM Volume vg1A is not available',
last-rc-change='Thu Nov 16 12:35:30 2017', queued=0ms, exec=36ms
It looks like the following constraints is no longer being taken into account which leads to a FAILED action :
Constraint: location-vg1A
Rule: score=-INFINITY (id:location-vg1A-rule)
Expression: #kind eq container (id:location-vg1A-rule-expr)
This problem is that some if not all resources on the guest nodes are not started anymore or fencing of the guest node could occur.
Environment
- Red Hat Enterprise Linux Server 7 (with the High Availability Add On)
pacemaker-1.1.16-12.el7_4.4or higher- The
pacemakercluster has guest nodes configured.
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.