Bug 1718368 - Deploying OSP-13 with TLS and composable networks fails due to hard-coded NovaLibvirtNetwork in nova-vnc-proxy.yaml
Summary: Deploying OSP-13 with TLS and composable networks fails due to hard-coded Nov...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: z8
: 13.0 (Queens)
Assignee: Ade Lee
QA Contact: Pavan
URL:
Whiteboard:
Depends On:
Blocks: 1719898
TreeView+ depends on / blocked
 
Reported: 2019-06-07 14:47 UTC by Irina Petrova
Modified: 2019-09-04 10:43 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.3.1-55
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1719898 1719899 (view as bug list)
Environment:
Last Closed: 2019-09-04 10:43:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 664503 0 None None None 2019-06-12 17:50:19 UTC

Description Irina Petrova 2019-06-07 14:47:57 UTC
Description of problem:

RHOSP-13 + TLS (on internal + external endpoints) + Composable Networks [1] fails like so:

overcloud.AllNodesDeploySteps.ControllerDeployment_Step1.1:
  resource_type: OS::Heat::StructuredDeployment
  physical_resource_id: ffeb8e36-a4c2-45d4-ac95-c7001842a2c1
  status: CREATE_FAILED
  status_reason: |
    Error: resources[1]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
  deploy_stdout: |
    ...
            "Warning: /Stage[main]/Tripleo::Certmonger::Ca::Crl/File[tripleo-ca-crl-file]: Skipping because of failed dependencies",
            "Warning: /Stage[main]/Tripleo::Certmonger::Ca::Crl/Exec[tripleo-ca-crl-process-command]: Skipping because of failed dependencies",
            "Warning: /Stage[main]/Tripleo::Certmonger::Ca::Crl/Cron[tripleo-refresh-crl-file]: Skipping because of failed dependencies"
        ]
    }
        to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/bd9cf002-47f8-4a4f-844c-eebdbbe5d3fd_playbook.retry

    PLAY RECAP *********************************************************************
    localhost                  : ok=23   changed=11   unreachable=0    failed=1

    (truncated, view all with --long)
  deploy_stderr: |

overcloud.AllNodesDeploySteps.ControllerDeployment_Step1.0:
  resource_type: OS::Heat::StructuredDeployment
  physical_resource_id: b92a2929-65b9-4d38-bef0-b3fb732b8aa5
  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: |
    ...
            "Warning: /Stage[main]/Tripleo::Certmonger::Ca::Crl/File[tripleo-ca-crl-file]: Skipping because of failed dependencies",
            "Warning: /Stage[main]/Tripleo::Certmonger::Ca::Crl/Exec[tripleo-ca-crl-process-command]: Skipping because of failed dependencies",
            "Warning: /Stage[main]/Tripleo::Certmonger::Ca::Crl/Cron[tripleo-refresh-crl-file]: Skipping because of failed dependencies"
        ]
    }
        to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/6739e88f-8cd2-447a-bf86-39c97d4485f6_playbook.retry

    PLAY RECAP *********************************************************************
    localhost                  : ok=24   changed=12   unreachable=0    failed=1


[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/spine_leaf_networking/


Version-Release number of selected component (if applicable):
RHOSP-13

Comment 4 Harry Rybacki 2019-06-13 12:06:38 UTC
Downstream review posted. Note, we are working to backport OSP13 fix prior to OSP15/14 due to Cu. requested HF.

Comment 5 Harry Rybacki 2019-06-13 13:59:37 UTC
Build complete. Updating FIV and moving RHBZ to MODIFIED.

Comment 8 Lon Hohberger 2019-07-11 10:41:05 UTC
According to our records, this should be resolved by openstack-tripleo-heat-templates-8.3.1-54.el7ost.  This build is available now.


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