Looks like the scale-up logic is outdated here: https://github.com/openstack/puppet-pacemaker/blob/658f4ee6d982169191531bd0daf6ef8e08f06ddc/manifests/corosync.pp#L223 It fails, i had to scale up manually via e.g. `pcs cluster node add controller-2 addr=172.17.1.11 --start --wait`. The error message produced is: "<13>Jul 1 16:53:28 puppet-user: Notice: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 to Cluster tripleo_cluster]/returns: Error: Cannot specify '--wait' without specifying '- -start'", "<13>Jul 1 16:53:28 puppet-user: Notice: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 to Cluster tripleo_cluster]/returns: Error: Errors have occurred, therefore pcs is unable to continue", "<13>Jul 1 16:53:28 puppet-user: Notice: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 to Cluster tripleo_cluster]/returns: No addresses specified for host 'controller-1', usin g 'controller-1'", "<13>Jul 1 16:53:28 puppet-user: Error: '/sbin/pcs cluster node add controller-1 --wait' returned 1 instead of one of [0]", "<13>Jul 1 16:53:28 puppet-user: Error: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 to Cluster tripleo_cluster]/returns: change from 'notrun' to ['0'] failed: '/sbin/pcs clus ter node add controller-1 --wait' returned 1 instead of one of [0]",
Upstream patch posted and tested manually.
Re-setting Target Milestone z1 to --- to begin the 15z1 Maintenance Release.
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/RHBA-2019:4030