Bug 1726694

Summary:	OSP 14->15: upgrade breaks -- outdated pacemaker scale-up logic missing `--start` and `addr=`
Product:	Red Hat OpenStack	Reporter:	Jiri Stransky <jstransk>
Component:	puppet-pacemaker	Assignee:	Jiri Stransky <jstransk>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	high
Version:	15.0 (Stein)	CC:	jjoyce, jschluet, lmiccini, michele, slinaber, tvignaud
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-pacemaker-0.7.3-0.20190807230458.8b30131.el8ost.noarch	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-02 10:11:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1727807

Description Jiri Stransky 2019-07-03 13:14:05 UTC

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]",

Comment 1 Jiri Stransky 2019-07-17 13:25:22 UTC

Upstream patch posted and tested manually.

Comment 3 Shelley Dunne 2019-09-19 18:29:48 UTC

Re-setting Target Milestone z1 to --- to begin the 15z1 Maintenance Release.

Comment 10 errata-xmlrpc 2019-12-02 10:11:16 UTC

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