Description of problem: For Openshift deployments we're using custom networks file which contains only External, InternalApi and the Storage network. We should provide such file in /usr/share/openstack-tripleo-heat-templates/network_data_openshift.yaml to be immediately available for the user to consume, otherwise it needs to be built manually which is not user friendly. Example of such network data file: [stack@undercloud-0 ~]$ cat network_data.yaml - name: Storage vip: true vlan: 30 name_lower: storage ip_subnet: '172.17.3.0/24' allocation_pools: [{'start': '172.17.3.10', 'end': '172.17.3.149'}] - name: InternalApi name_lower: internal_api vip: true vlan: 20 ip_subnet: '172.17.1.0/24' allocation_pools: [{'start': '172.17.1.10', 'end': '172.17.1.149'}] - name: External vip: true name_lower: external ip_subnet: '10.0.0.0/24' allocation_pools: [{'start': '10.0.0.101', 'end': '10.0.0.149'}] gateway_ip: '10.0.0.1' Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-9.0.0-0.20180919080939.888743c.0rc1.el7ost.noarch How reproducible: 100%
Submitted upstream change at https://review.openstack.org/#/c/613864/
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-2019:0045