Created attachment 1358034 [details] logs & config from undercloud Description of problem: Failed during upgrade from OSP11 SRIOV - Composable role setup to latest OSP12 vercloud.AllNodesDeploySteps.AllNodesPostUpgradeSteps.ControllerDeployment_Step3.0: resource_type: OS::Heat::StructuredDeployment physical_resource_id: 52cefde5-d2a4-4c31-a12b-ec2af27228bb status: CREATE_FAILED status_reason: | Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2 deploy_stdout: | PLAY [localhost] *************************************************************** TASK [Gathering Facts] ********************************************************* ok: [localhost] TASK [Set host puppet debugging fact string] *********************************** ok: [localhost] TASK [Write the config_step hieradata] ***************************************** changed: [localhost] TASK [Run puppet host configuration for step 3] ******************************** ok: [localhost] TASK [debug] ******************************************************************* fatal: [localhost]: FAILED! => { "(outputs.stderr|default('')).split('\n')|union(outputs.stdout_lines|default([]))": [ "exception: connect failed", "Warning: Undefined variable 'deploy_config_name'; ", " (file & line not available)", Version-Release number of selected component (if applicable): rpm -qa |grep triple openstack-tripleo-validations-7.4.2-1.el7ost.noarch python-tripleoclient-7.3.3-4.el7ost.noarch openstack-tripleo-image-elements-7.0.1-1.el7ost.noarch puppet-tripleo-7.4.3-7.el7ost.noarch openstack-tripleo-common-containers-7.6.3-3.el7ost.noarch openstack-tripleo-common-7.6.3-3.el7ost.noarch openstack-tripleo-ui-7.4.3-4.el7ost.noarch openstack-tripleo-puppet-elements-7.0.1-1.el7ost.noarch openstack-tripleo-heat-templates-7.0.3-10.el7ost.noarch How reproducible: always Steps to Reproduce: 1.Deploy OSP-11 sriov with Composable role 2.Run upgrade to osp12 use this guide: https://gitlab.cee.redhat.com/mcornea/OSP11-OSP12-Upgrade/blob/master/README.md 3. Actual results: failed Expected results: Additional info: Logs attached
The failure related to those bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1516275 https://bugzilla.redhat.com/show_bug.cgi?id=1507225
I checked the environment and the failure was caused by the overcloud nodes not being able to reach the undercloud Docker registry. This was caused by the undercloud missing allowing firewall access for port tcp 8787 which looks pretty much similar to bug 1507225 except that 1507225 was reported for a different port.
So this is most likely duplicate, can you confirm?
(In reply to Lukas Bezdicka from comment #3) > So this is most likely duplicate, can you confirm? Yes.
Closing as per comment 4 *** This bug has been marked as a duplicate of bug 1507225 ***