Red Hat Bugzilla – Bug 1237329
Overcloud: HA: Pacemaker and ironic fighting for control causing fencing to fail when rebooting/powering off the node.
Last modified: 2015-08-05 09:57:56 EDT
Overcloud: HA: Pacemaker and ironic fighting for control causing fencing to fail when using ironic to power off the node. pacemaker is trying to turn the node off (or on) using fencing while ironic is trying to return the node to correct state. We have to configure Ironic to *not* try to restore the node to a correct power state and let the pacemaker do the job.
The work around: 1.on the instack node edit /etc/ironic/ironic.conf file 2.Uncomment force_power_state_during_sync and set it to false. 3.restart openstack-ironic-conductor service.
Lucas, can you make sure you default to having the force_power_state_during_sync to false and make sure there are docs describing how to turn it on if needed?
@Chris, will do! @Leonid, that's not a workaround, that's the right way to do. Ironic by default will try to make sure that the machines are in sync with the database state. But we made it configurable for this kinda of situations.
Btw, we don't have any fencing agent for Ironic in Peacemaker right? If Peacemaker used the Ironic interface to power on and off the nodes it's fencing this problem wouldn't happen.
Lucas, a question on the gerrithub review about the use of tabs there. If that needs to be fixed, can you update the patch? once it's in shape, please submit to code.engineering as well.
upstream and downstream patches merged
ironic.conf includes force_power_state_during_sync=False instack-undercloud-2.1.2-21.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1549