Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1643308

Summary:	Director deployed OCP 3.11 re-running overcloud deploy fails with "msg": "Please run playbooks/openshift-master/scaleup.yml if you need to scale up both masters and nodes. This playbook is only needed if you are only adding new nodes and not new masters
Product:	Red Hat OpenStack	Reporter:	Marius Cornea <mcornea>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin André <m.andre>
Status:	CLOSED ERRATA	QA Contact:	Gurenko Alex <agurenko>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	dbecker, m.andre, mburns, morazi, racedoro
Target Milestone:	rc	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-9.0.1-0.20181013060882.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:54:26 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:

Description Marius Cornea 2018-10-25 22:07:41 UTC

Description of problem:

Director deployed OCP 3.11 re-running overcloud deploy with the openshift_storage_glusterfs_heketi_admin_key param included as workaround for BZ#1640382 fails with "msg": "Please run playbooks/openshift-master/scaleup.yml if you need to scale up both masters and nodes.  This playbook is only needed if you are only adding new nodes and not new masters

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-9.0.1-0.20181013060864.ffbe879.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy OCP with 3 masters + 3 workers + 3 infra nodes with CNS enable
2. Add openshift_storage_glusterfs_heketi_admin_key to an environment file by pulling its value from the existing deployment
3. Re-run overcloud deploy.

Actual results:
Failure.

Expected results:
No failures, this should be a noop operation.

Additional info:
Attaching /var/lib/mistral/openshift

Comment 2 Martin André 2018-10-29 08:42:15 UTC

There are two issues at play here:
1) re-running the same deploy command without new nodes added to the deployment shouldn't trigger the scale up. Fixing upstream with https://review.openstack.org/#/c/613637/.
2) master scale up and node scale up playbooks are exclusive. Fixing upstream with https://review.openstack.org/#/c/613641/.

Comment 21 Martin André 2019-01-10 10:20:14 UTC

No doc text required.

Comment 22 errata-xmlrpc 2019-01-11 11:54:26 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/RHEA-2019:0045