Description of problem: The pacemaker stonith-property is set to false after an upgrade from RHOS9 to RHOS10 even though it was set to true before upgrade - This causes fencing to be disable so fencing of overcloud nodes does not work properly especially in split-brain condition Version-Release number of selected component (if applicable): puppet-tripleo-5.2.0-2.el7ost.noarch openstack-tripleo-common-5.2.1-0.20161007114757.cc19d04.el7ost.noarch openstack-tripleo-heat-templates-5.0.0-0.20161008015357.0d3e3e3.1.el7ost.noarch openstack-tripleo-puppet-elements-5.0.0-0.20161003213431.200d011.el7ost.noarch python-tripleoclient-5.2.0-2.el7ost.noarch openstack-tripleo-image-elements-5.0.0-1.el7ost.noarch openstack-tripleo-0.0.8-0.2.4de13b3git.el7ost.noarch openstack-tripleo-heat-templates-compat-2.0.0-34.3.el7ost.noarch openstack-tripleo-ui-1.0.3-1.el7ost.noarch How reproducible: Always (presumably), The condition seems to be racy. Steps to Reproduce: 1. Deploy RHOS9 - set stonith-enabled to true (pcs property set stonith-enabled=true) 2. Upgrade to RHOS10 Actual results: stonith-enabled is false Expected results: stonith-enabled should keep the state - true Additional info:
Marian, could you give the attached gerrit patch a spin and report back please? Thanks
(In reply to Michele Baldessari from comment #1) > Marian, could you give the attached gerrit patch a spin and report back > please? Thanks I tried to perform "major upgrade step" with patched major_upgrade_controller_pacemaker_1.sh and It seems to work correctly, even though I did perform only the major upgrade step, I was watching tje status of stonith-enabled property and could verify that It was switched to false and then again properly switched to true and kept that way.
Stable/newton change has merged
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://rhn.redhat.com/errata/RHEA-2016-2948.html