Bug 1516634 - OSP11 -> OSP12 upgrade SRIOV Composable role failed
Summary: OSP11 -> OSP12 upgrade SRIOV Composable role failed
Keywords:
Status: CLOSED DUPLICATE of bug 1507225
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Lukas Bezdicka
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On: 1507225 1516275
Blocks: 1516952
TreeView+ depends on / blocked
 
Reported: 2017-11-23 07:08 UTC by Eran Kuris
Modified: 2017-11-29 12:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-29 12:06:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs & config from undercloud (725.52 KB, application/x-gzip)
2017-11-23 07:08 UTC, Eran Kuris
no flags Details

Description Eran Kuris 2017-11-23 07:08:08 UTC
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

Comment 1 Eran Kuris 2017-11-23 09:44:38 UTC
The failure related to those bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1516275
https://bugzilla.redhat.com/show_bug.cgi?id=1507225

Comment 2 Marius Cornea 2017-11-23 10:55:15 UTC
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.

Comment 3 Lukas Bezdicka 2017-11-23 14:37:30 UTC
So this is most likely duplicate, can you confirm?

Comment 4 Eran Kuris 2017-11-23 15:04:33 UTC
(In reply to Lukas Bezdicka from comment #3)
> So this is most likely duplicate, can you confirm?

Yes.

Comment 5 Jakub Libosvar 2017-11-29 12:06:54 UTC
Closing as per comment 4

*** This bug has been marked as a duplicate of bug 1507225 ***


Note You need to log in before you can comment on or make changes to this bug.