Red Hat Bugzilla – Bug 1406869
Pacemaker is not enabled by default in overcloud HA deployment
Last modified: 2017-05-17 15:52:01 EDT
[stack@undercloud-0 ~]$ grep OS::TripleO::Services::Pacemaker /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.j2.yaml OS::TripleO::Services::Pacemaker: OS::Heat::None [stack@undercloud-0 ~]$ rpm -qa | grep tripleo-heat-templates openstack-tripleo-heat-templates-6.0.0-0.20161130195427.9cd0c5a.el7ost.noarch
I think a sensible plan here is to add a downstream only change of the defaults (as we did in the past) to fix this issue in the meantime. I will also start a discussion upstream around this so hopefully we can default to that for the future. For the downstream-only though I would need a rhos-11-patches branch created for tht. Setting needinfo on Mike to see if this can be done
Hey Marius, can we test this?
(In reply to Carlos Camacho from comment #5) > Hey Marius, can we test this? Hey Carlos! Sure we can but if I understand it correctly there is also an upstream patch https://review.openstack.org/359060 which enables pacemaker by default so it's not clear to me if we should test the downstream patch attached to this BZ or the upstream one. Please let me know. Thanks!
Hey Marius, yeahp I think the upstream patch will be merged soon, I already tested the downstream fix, but I think won't be needed.
Carlos, since there seems to be quite a bit of CI wrangling to be done upstream to get it in and I am not yet sure I will find the time, can we in the meantime merge the downstream patch (aka remove the -2 from the review) and if we manage the upstream patch then we can talk to mburns and get this downstream one dropped. If we won't make the cut then we're already set. What do you think? thanks, Michele
Hey Michele, you are right there, +2ed.
Downstream changed merged. I will ping Mike should we manage to do it upstream as well before release time
Verified: openstack-tripleo-heat-templates-6.0.0-0.20170214010958.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-2017:1245