Description of problem: ----------------------- Attempt to update failed with a message: [DEBUG] Error: Stopping the node will cause a loss of the quorum, use --force to override [ERROR] Error running /var/lib/heat-config/heat-config-script/c3bdb14e-6c0b-48a9-96c6-0bd7cb9ecf9f. [1] [INFO] Completed /usr/libexec/heat-config/hooks/script At the same time update was already running on another controller node. Version-Release number of selected component (if applicable): -------------------------------------------------------------- openstack-tripleo-heat-templates-6.0.0-0.20170127041112.ce54697.el7ost.1.noarch openstack-heat-templates-0.0.1-0.20170124165609.15cf0b6.el7ost.noarch python-openstack-mistral-4.0.0-0.20170126231245.47efc0f.el7ost.noarch openstack-mistral-engine-4.0.0-0.20170126231245.47efc0f.el7ost.noarch openstack-mistral-api-4.0.0-0.20170126231245.47efc0f.el7ost.noarch openstack-mistral-common-4.0.0-0.20170126231245.47efc0f.el7ost.noarch puppet-mistral-10.1.0-0.20170123224219.22afb8b.el7ost.noarch openstack-mistral-executor-4.0.0-0.20170126231245.47efc0f.el7ost.noarch python-mistralclient-3.0.0-0.20170120193250.a7bf138.el7ost.noarch Steps to Reproduce: 1. Install RHOS-11 puddle 2017-02-01.2 2. Setup latest RHOS-11 repos 3. Update undercloud 4. Try to update overcloud Actual results: --------------- yes '' | openstack overcloud update stack -i overcloud Started Mistral Workflow tripleo.package_update.v1.package_update_plan. Execution ID: 1270370f-408c-4ee3-8e22-dd462e42cfe6 Waiting for messages on queue 'ddfd6d25-15ac-4915-8370-803f916c44a8' with no timeout. IN_PROGRESS IN_PROGRESS FAILED update finished with status FAILED Stack update failed. Additional info: ---------------- Virtual setup: 3controllers + 1compute + 3ceph
https://review.openstack.org/#/c/432357/ fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1420372
Update succeeded with openstack-tripleo-common-6.0.0-6.el7ost.noarch
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-2017:1245