Description of problem:
Pacemaker is not enabled by default in overcloud HA deployment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy overcloud with the following command:
openstack overcloud deploy --templates \
-e $THT/environments/network-isolation.yaml \
-e $THT/environments/network-management.yaml \
-e ~/templates/network-environment.yaml \
-e $THT/environments/storage-environment.yaml \
-e ~/templates/disk-layout.yaml \
-e ~/templates/wipe-disk-env.yaml \
--control-scale 3 \
--control-flavor controller \
--compute-scale 1 \
--compute-flavor compute \
--ceph-storage-scale 1 \
--ceph-storage-flavor ceph \
--ntp-server clock.redhat.com \
Deployment fails at CREATE_FAILED Error: resources.ControllerNodesPostDeployment.resources.ControllerOvercloudServicesDeployment_Step3.resources
When I log in to one of the controllers I can see that:
[root@overcloud-controller-0 ~]# pcs status
Error: cluster is not currently running on this node
Pass -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml
*** Bug 1355597 has been marked as a duplicate of this bug. ***
I'm testing the lastest build:
I can see in overcloud-resource-registry-puppet.yaml that pacemaker is set only for a set of resources:
grep pacemaker /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml
# set to controller-config-pacemaker.yaml to enable pacemaker
While environments/puppet-pacemaker.yaml also contains entries for the custom pacemaker services:
[root@undercloud openstack-tripleo-heat-templates]# cat environments/puppet-pacemaker.yaml
# An environment which enables configuration of an
# Overcloud controller with Pacemaker.
# custom pacemaker services
# NOTE: For now we will need to specify overrides to all services
# which use pacemaker. In the future (with upcoming HA light work) this
# list will hopefully be much smaller however.
# Neutron Core Plugin Vendors (these typically override NeutronCorePlugin)
ccamacho is going to take a look at this. he is working on getting setup with the downstream patching process and gerrit.
Hello, I have updated the overcloud-resource-registry template with the values from the puppet-pacemaker deployment.
Locally working for me by:
openstack overcloud deploy \
--libvirt-type qemu \
--ntp-server pool.ntp.org \
--control-scale 3 \
--templates /home/stack/openstack-tripleo-heat-templates \
This is adding by default adding the parameters currently in puppet-pacemaker.yaml
I had some doubts about doing this in this way, as this will break all non-pacemaker deployments, but now I'm aware of the fact that that's the only option supported downstream.
Even that my initial thought was to update instead the python-tripleo client so when used any *-scale option automatically appends the puppet-pacemaker template.
(In reply to Carlos Camacho from comment #7)
> I had some doubts about doing this in this way, as this will break all
> non-pacemaker deployments, but now I'm aware of the fact that that's the
> only option supported downstream.
> Even that my initial thought was to update instead the python-tripleo client
> so when used any *-scale option automatically appends the puppet-pacemaker
That sounds like it could get accepted upstream as well.
Take into account that all pcm templates should disappear when the new HA lands.
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.