Stack Update error when changeing network/subnet properties

[Harald Jensås]

ERROR on stack update:

ResourceActionNotSupported: resources.BaremetalSubnet: Updating the subnet segment assciation only allowed when the current segment_id is None. The subnet is currently associated with segment. In this state update is not supported for resource.

This error occured on stack update after changeing subnet properties.

Debugging reveals that the list of segments, where we rely on index 0 being the base segment created behind the scenes by OS::Neutron::Net resources is not predictable.

The '{get_attr: [{{network.name}}Network, segments, 0, id]}' call can return the segment_id of a leaf subnet in a DCN or spine-leaf deployment.

[Harald Jensås (harald-jensas)]

Attempting to fix this with yaql did not work out due to heat bug: https://storyboard.openstack.org/#!/story/1705216#comment-164247

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat 16.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat 14.2.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat 15.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat train-eol release.