Description of problem: This looks like another occurrence of an OSP-12 bug that was allegedly fixed in bug #1488905. A user is trying to upgrade their OSP-12 cloud to OSP-13 following these access.redhat.com guides: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/upgrading_red_hat_openstack_platform/ https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html/upgrading_red_hat_openstack_platform/keeping_openstack_platform_updated#keeping_the_undercloud_updated The user has the latest OSP-12 bits. First they update their undercloud, then attempt a minor overcloud update. This is the error they see: $ openstack overcloud update stack --init-minor-update \ --container-registry-file /home/stack/templates/overcloud_images.yaml Stack overcloud UPDATE_FAILED overcloud.AllNodesDeploySteps.WorkflowTasks_Step2_Execution: resource_type: OS::Mistral::ExternalResource physical_resource_id: dbc5309f-045e-4446-adde-5c152b53efab status: UPDATE_FAILED status_reason: | StackValidationFailed: resources.WorkflowTasks_Step2_Execution: Property error: Properties.actions.CREATE.workflow: Error validating value 'tripleo.overcloud.workflow_tasks.step2': The Workflow (tripleo.overcloud.workflow_tasks.step2) could not be found. Heat Stack update failed. It was suggested that he try re-running "openstack undercloud install" to regenerate the missing Mistral workflows, but this did not help. Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates.noarch 7.0.12-17.el7ost openstack-mistral-executor.noarch 5.2.3-1.el7ost python-mistral-lib.noarch 0.3.3-1.el7ost openstack-mistral-common.noarch 5.2.3-1.el7ost python-mistralclient.noarch 3.1.4-1.el7ost python-mistral.noarch 5.2.3-1.el7ost openstack-mistral-api.noarch 5.2.3-1.el7ost puppet-mistral.noarch 11.4.0-2.el7ost openstack-mistral-engine.noarch 5.2.3-1.el7os instack-undercloud.noarch 7.4.12-3.el7ost openstack-tripleo-common.noarch 7.6.13-6.el7ost openstack-tripleo-common-containers.noarch 7.6.13-6.el7ost How reproducible: Unknown. User has not been able to tear down environment and try from scratch as described below, due to operational constraints. Steps to Reproduce: 1. Install new OSP-12 undercloud and deploy an overcloud 2. Follow OSP-12-to-13 upgrade guide 3. Run "openstack overcloud update stack --init-minor-update --container-registry-file /home/stack/templates/overcloud_images.yaml" and see error Actual results: Overcloud stack update failed. Expected results: Undercloud and overcloud updated to OSP-13.
*** This bug has been marked as a duplicate of bug 1488905 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days