instack-undercloud: one controller deployment: running "pcs status" - Error: cluster is not currently running on this node Environment: pcs-0.9.137-13.el7_1.2.x86_64 instack-undercloud-2.1.2-dev8.el7.centos.noarch Steps to reproduce: 1. Deploy overcloud with one controller. 2. Login to the controller and run "pcs status" Result: Error: cluster is not currently running on this node Expected result: No errors.
hi, can you check if you have the following: https://github.com/rdo-management/tripleo-heat-templates/commit/edf29c16e0473f9d96d3d55b0b28f67de5a624bc in /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml ?
Checked, the change isn't there.
While the 'pcs' command is installed by default in the overcloud images, to make the Director setup a Pacemaker cluster on the controller nodes one needs to pass the following to the deploy command: -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml without it, the Pacemaker cluster is not going to be created.