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:1738
Verified on compose 2019-06-13.2 Steps to verify: 1. Mark UpdateDeployment for Controller-0 as unhealthy . stackrc openstack stack resource list overcloud -n 3| grep UpdateDeployment openstack stack list --nested | grep overcloud-Controller-mjjfhihtidvh-0-cqibtjz5mdjw openstack stack resource mark unhealthy a0ef511c-cbe4-4159-a7c3-9cd4337d4782 UpdateDeployment 2. Create a new environment file blacklist.yaml with content: parameter_defaults: DeploymentServerBlacklist: - controller-0 3. Stop correlating vm by virsh shutdown on the hyperviser 4. Deploy with the new environment file #add to overcloud_deploy.sh -e /home/stack/blacklist.yaml \ #execute ./overcloud_deploy.sh ... 2019-06-20 06:48:06Z [AllNodesDeploySteps]: UPDATE_COMPLETE state changed 2019-06-20 06:48:12Z [overcloud]: UPDATE_COMPLETE Stack UPDATE completed successfully Stack overcloud UPDATE_COMPLETE Started Mistral Workflow tripleo.deployment.v1.get_horizon_url. Execution ID: 3c86a304-3075-4047-997f-2c827377961a Overcloud Endpoint: https://10.0.0.101:13000/ Overcloud Horizon Dashboard URL: https://10.0.0.101:443/dashboard Overcloud rc file: /home/stack/overcloudrc Overcloud Deployed