Deployment with custom network names fails due to mismatch in subnet names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Harald Jensås |
Bug Description
Deployment with custom network names fails due to mismatch in subnet names.
Custom network data with renamed name_lower for network.
- name: InternalApi
name_lower: MyInternalApiNet
service_
vip: true
vlan: 20
ip_subnet: '172.16.2.0/24'
openstack overcloud deploy \
< .. snip .. >
-n /home/stack/
< .. snip .. >
No custom roles data file.
The deployment fails with:
overcloud.
resource_type: OS::TripleO:
physical_
status: CREATE_FAILED
status_reason: |
resources.
This happens because the subnet specified in roles_data.yaml[1] is'nt updated to match the renamed name_lower for the InternalApi network.
https:/
Changed in tripleo: | |
status: | Triaged → In Progress |
Fix proposed: https:/ /review. opendev. org/664988