Bug 2037418

Summary: osp17 deployment fails without network pre-provision
Product: Red Hat OpenStack Reporter: Ella Shulman <eshulman>
Component: openstack-tripleoAssignee: James Slagle <jslagle>
Status: CLOSED NOTABUG QA Contact: Joe H. Rahme <jhakimra>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 17.0 (Wallaby)CC: hakhande, hjensas, mburns, oblaut, sbaker, skramaja
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-11 21:46:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
tempaltes used for deployment none

Description Ella Shulman 2022-01-05 15:54:15 UTC
Created attachment 1849050 [details]
tempaltes used for deployment

Description of problem:
OSP 17 deployment fails if network pre-provision is not used

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

How reproducible:
100%

Steps to Reproduce:
1.deploy overcloud without pre-provisioning the network


Actual results:
deployment fails

Expected results:
working deployment

Additional info:
I used the same templates with pre-provision and it worked. without this bug fixed we will be unable to deploy nfv having that network pre-provision causes dpdk to fail due to kargs not being configured

Comment 3 Steve Baker 2022-01-11 21:46:03 UTC
This looks like a duplicate

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

Comment 4 Harald Jensås 2022-01-11 21:56:42 UTC
So you are trying to deploy using the "all-in-one" overcloud deploy command as described here[1]?

Looking at the deploy command it seems you are not provisioning the VIPs for the isolated networks?
No '--vip-file' option used, so you end up with only the ctlplane VIP. 

The error is "Gateway Timeout (HTTP 504)" in "Clean up legacy Cinder keystone catalog entries" task.
Seems the missing VIPs could be the problem?


openstack overcloud deploy \
  --templates /usr/share/openstack-tripleo-heat-templates \
  --stack overcloud \
 --ntp-server clock1.rdu2.redhat.com \
  --roles-file /home/stack/ospd_no_nfv/roles/roles_data.yaml \
  --deployed-server \
  --baremetal-deployment /home/stack/ospd_no_nfv/network/baremetal_deployment.yaml \
  -n /home/stack/ospd_no_nfv/network/network_data_v2.yaml \
  --environment-file /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovs.yaml \
  -e /home/stack/ospd_no_nfv/network-environment-overrides.yaml \
  -e /home/stack/containers-prepare-parameter.yaml \
  --log-file overcloud_deployment.log

@Ella, Can you try adding '--vip-file /home/stack/ospd_no_nfv/network/vip_data.yaml' to the deploy command?

Since you are not using '--network-config' in the command, os-net-config will not run as part of the baremetal provisioning step, so the kernel args and tuned should be configured prior to os-net-config run in this case.


NOTE: The "all-in-one" is not what we intend to document and recommend to our customers. It may be better to convert the job to pre-provision with '--network-config' and use the fixes for bug 2035325 to ensure the kernel args and tuned is configured.


[1] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/network_v2.html#the-all-in-one-alternative-using-overcloud-deploy-command

Comment 5 Ella Shulman 2022-01-18 08:01:35 UTC
Hi we are not trying to deploy all in one, it is a regular deployment. It will take me some time to verify but what you are saying make sense and probably is the issue.