On Tue, 2023-04-11 at 14:05 +0000, Sahid Orentino wrote:
> Hum... line 33 and 45 of [0] we can see that your networks are not
> attached to any segments. It is not expected that the code go through
> the point that you are mentioning on comment #7, see [1].
>
> anychance that you print network.segments ? In all cases I will check
> the code to understand what's going on...
I applied this change[0] which produced this output [1] (this is a different environment, so the
list/show for network, subnet and segments are [2] in case you need to cross reference the UUIDs)
The network that has associated a segment with the segment_id set to None is of network_type flat:
On Tue, 2023-04-11 at 14:05 +0000, Sahid Orentino wrote:
> Hum... line 33 and 45 of [0] we can see that your networks are not
> attached to any segments. It is not expected that the code go through
> the point that you are mentioning on comment #7, see [1].
>
> anychance that you print network.segments ? In all cases I will check
> the code to understand what's going on...
I applied this change[0] which produced this output [1] (this is a different environment, so the
list/show for network, subnet and segments are [2] in case you need to cross reference the UUIDs)
The network that has associated a segment with the segment_id set to None is of network_type flat:
network: 9eb0c107- fc1b-494b- 922a-645c2f728f c3 'juju-aae23a- jammy-antelope- 8.project. serverstack' ,
'juju- aae23a- jammy-antelope- 9.project. serverstack' ],
id=9fa37738- 1cd1-48bf- 8d2b-426bd65216 f6,
is_dynamic= False,
network_ id=9eb0c107- fc1b-494b- 922a-645c2f728f c3,
network_ type=flat,
physical_ network= physnet1,
segment_ index=0,
segmentation_ id=None
segment: hosts=[
name=None,
[0] https:/ /pastebin. ubuntu. com/p/qRWwZFwcp H/ /pastebin. ubuntu. com/p/hdRZmjDFv s/ /pastebin. ubuntu. com/p/VCmBfyZyR k/
[1] https:/
[2] https:/