Hide Forgot
Description of problem: When using composable networks and adding a custom network the cloud_name parameter is not created for that network. A jinja loop needs to be added to all-nodes-config.j2.yaml. Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-7.0.3-17.el7ost.noarch How reproducible: Every time. Steps to Reproduce: 1. Deploy an overcloud. 2. ssh to the controller node 3. Check for cloud_name parameters for the networks [heat-admin@overcloud-controller-0 ~]$ sudo grep -r cloud_name /var/lib/./config-data/haproxy/etc/puppet/hieradata /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_ctlplane": "overcloud.ctlplane.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_external": "overcloud.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_internal_api": "overcloud.internalapi.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_storage": "overcloud.storage.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_storage_mgmt": "overcloud.storagemgmt.localdomain", Actual results: no parameter for new OcProvisioning network. Expected results: Should be a cloud_name parameter. Additional info:
Verify using puddle : 2018-04-10.2 Env: (undercloud) [stack@host01 ~]$ rpm -q openstack-tripleo-heat-templates openstack-tripleo-heat-templates-8.0.2-0.20180327213846.el7ost.noarch There is a composable role defined in network_data.yaml (undercloud) [stack@host01 ~]$ tail -9 network_data.yaml - name: OcProvisioning name_lower: oc_provisioning vip: true vlan: 205 ip_subnet: '172.21.2.0/24' allocation_pools: [{'start': '172.21.2.10', 'end': '172.21.2.200'}] ipv6_subnet: 'fd00:fd00:fd00:7000::/64' ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:7000::10', 'end': 'fd00:fd00:fd00:7000:ffff:ffff:ffff:fffe'}] [root@overcloud-controller-0 ~]# sudo grep -r cloud_name /var/lib/./config-data/haproxy/etc/puppet/hieradata /var/lib/./config-data/haproxy/etc/puppet/hieradata/service_configs.json: "neutron::agents::metadata::metadata_host": "%{hiera('cloud_name_internal_api')}", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_ctlplane": "overcloud.ctlplane.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_external": "overcloud.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_internal_api": "overcloud.internalapi.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_oc_provisioning": "overcloud.ocprovisioning.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_storage": "overcloud.storage.localdomain", /var/lib/./config-data/haproxy/etc/puppet/hieradata/vip_data.json: "cloud_name_storage_mgmt": "overcloud.storagemgmt.localdomain",
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086