Harald Jensås 546bc23915 Net attr: Sort segments without name attribute first ... Useing get_attr, pulling index 0 in the segments list of a network to associate the a subnet with the "first" segment is useful since the "first" segment is created by neutron behind the scenes on network create. A resource reference cannot be used since the "first" segment is'nt a heat resource. The issue is the order of the segments list is'nt reliable. On stack update index 0 may be a different segment, and we end up trying to update the segment_id for a subnet. Changeing the segment association is not allowed, so the stack update fails. While not perfect, sorting the list so that segments where name is None comes first will ensure that index 0 can be used. The template author should ensure segments defined in the heat template all have a names set, so that only the segment creted implicitly by neutron have 'None' name. Closes-Bug: #1894920 Change-Id: I097aba2a97144327bec188e6c71629d0f6c95901 (cherry picked from commit 539b2a4c49)		2021-03-05 01:17:54 +00:00
..
notes	Net attr: Sort segments without name attribute first	2021-03-05 01:17:54 +00:00
source	Imported Translations from Zanata	2020-06-17 07:27:09 +00:00