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
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/.
No doc text required.
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