-
Bug
-
Resolution: Unresolved
-
Major
-
rhos-18.0 Beta, rhos-18.0.4
-
None
-
8
-
False
-
-
False
-
?
-
openstack-neutron-22.2.2-18.0.20250220204730.51e19bb.el9osttrunk
-
None
-
-
-
-
Important
My environment contains one Routed Provider Network, with 3 segments
First step
I created the Routed Provider Network, with 3 associated segments.
The OpenStack command shows the following output:
$ openstack network list -c ID -c Name +--------------------------------------+----------------------+ | ID | Name | +--------------------------------------+----------------------+ | 7fa6ba7f-eba5-452e-87cc-fca7637475f8 | net1 | +--------------------------------------+----------------------+ $ openstack network segment list -c ID -c Name --network 7fa6ba7f-eba5-452e-87cc-fca7637475f8 +--------------------------------------+-------------------+ | ID | Name | +--------------------------------------+-------------------+ | 0dfd3828-9527-45a2-83f7-bcf79e6390a6 | net1-seg1 | | 274a4c30-e15b-4751-b1cf-772d2b4620de | net1-seg2 | | 565b3c4a-e996-4def-89a4-df62e7df7bcd | net1-seg3 | +--------------------------------------+-------------------+ $ openstack aggregate list -c ID -c Name +----+---------------------------------------------------------+ | ID | Name | +----+---------------------------------------------------------+ | 50 | Neutron segment id 274a4c30-e15b-4751-b1cf-772d2b4620de | | 53 | Neutron segment id 0dfd3828-9527-45a2-83f7-bcf79e6390a6 | | 54 | Neutron segment id 565b3c4a-e996-4def-89a4-df62e7df7bcd | +----+---------------------------------------------------------+
When I verified, my compute nodes were automatically added to the right segment aggregates, as follows:
$ openstack aggregate show 50
-----------------{}-------------------------------------------------------+
Field | Value |
-----------------{}-------------------------------------------------------+
availability_zone | None |
created_at | 2024-07-09T19:50:48.000000 |
deleted_at | None |
hosts | compute1 , compute2 |
id | 50 |
is_deleted | False |
name | Neutron segment id 274a4c30-e15b-4751-b1cf-772d2b4620de |
properties | |
updated_at | None |
uuid | 93e1dc9c-1ff5-48d1-8f68-964f3eff80c7 |
-----------------{}-------------------------------------------------------+
Second step
Network segments were already created as I described in the first step.
I deployed and added new compute nodes in my environment. However, they weren't automatically added to the expected associated segments.
I added them manually. Then, I tried to create new Virtual Machines on those compute nodes. The Virtual Machines were not created cause of network issues.
Workaround
I deleted the network segment related to those compute nodes. After that, I found my compute nodes automatically added to that segment aggregate
- is cloned by
-
OSPRH-17553 [Routed Provider Networks] : New Compute nodes are not added to their segment aggregate
-
- Review
-
- links to