InternalApi heat resource renamed to Internal

Bug #1718765 reported by Tim Rozet
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Undecided
Unassigned

Bug Description

With the new way of dynamically generating networks via the network_data.yaml file:
https://github.com/openstack/tripleo-heat-templates/blob/master/network_data.yaml

The heat resource OS::Tripleo::Network::InternalApi has been renamed to OS::Tripleo::Network::Internal. This breaks backwards compatibility when using previous heat templates with resource registry entries that override that resource. Such as:

resource_registry:
  OS::TripleO::Network::External: |-
     /usr/share/openstack-tripleo-heat-templates/network/external.yaml
  OS::TripleO::Network::InternalApi: OS::Heat::None

The cause of this renaming is due to InternalApi network having compat_name:
https://github.com/openstack/tripleo-heat-templates/blob/master/network_data.yaml#L61

As it is used to create the resource registry via j2:
https://github.com/openstack/tripleo-heat-templates/blob/stable/pike/network/networks.j2.yaml#L7

By removing compat_name for InternalApi network, the problem is fixed.

Revision history for this message
Tim Rozet (trozet) wrote :

Accidentally filed this twice. Dupe of 1718764

Changed in tripleo:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.