Bug 2013820
Summary: | OVN with dhcp-agent - assigning segment to a subnet removes DHCP IPs / agents | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Chris Janiszewski <cjanisze> |
Component: | python-networking-ovn | Assignee: | Rodolfo Alonso <ralonsoh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Eran Kuris <ekuris> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 16.2 (Train) | CC: | apevec, cjanisze, dsorrent, egarciar, fyanac, lhh, majopela, scohen |
Target Milestone: | z2 | Keywords: | TestOnly, Triaged |
Target Release: | 16.2 (Train on RHEL 8.4) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-networking-ovn-7.4.2-0.20220127234927.3a1deba.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-12-05 12:45:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Janiszewski
2021-10-13 20:23:18 UTC
I was able to recreate this in my lab and found relatively simple workaround. The original script for creating these baremetal routed networks has been like this: openstack network create oc_provisioning --provider-network-type flat --provider-physical-network provider0 --share --external --mtu 1500 SID=$(openstack network segment list --network oc_provisioning -c ID -f value) openstack network segment set --name segment0 ${SID} # <-------- this is the line where the problem occurs openstack network segment create --network oc_provisioning --physical-network provider1 --network-type flat segment1 openstack network segment create --network oc_provisioning --physical-network provider2 --network-type flat segment2 openstack subnet create --network-segment segment0 --network oc_provisioning --subnet-range 10.60.0.0/24 --dhcp --allocation-pool start=10.60.0.100,end=10.60.0.199 --gateway=10.60.0.1 oc_provisioning-seg0 openstack subnet create --network-segment segment1 --network oc_provisioning --subnet-range 10.60.1.0/24 --dhcp --allocation-pool start=10.60.1.100,end=10.60.1.199 --gateway=10.60.1.1 oc_provisioning-seg1 openstack subnet create --network-segment segment2 --network oc_provisioning --subnet-range 10.60.2.0/24 --dhcp --allocation-pool start=10.60.2.100,end=10.60.2.199 --gateway=10.60.2.1 oc_provisioning-seg2 .. and here is the modified script that result in all the segments being created properly with corresponding dhcp servers: openstack network create oc_provisioning --provider-network-type flat --provider-physical-network provider0 --share --external --mtu 1500 SID=$(openstack network segment list --network oc_provisioning -c ID -f value) openstack network segment set --name segment0 ${SID} openstack network segment create --network oc_provisioning --physical-network provider1 --network-type flat segment1 openstack network segment create --network oc_provisioning --physical-network provider2 --network-type flat segment2 openstack subnet create --network-segment segment1 --network oc_provisioning --subnet-range 10.60.1.0/24 --dhcp --allocation-pool start=10.60.1.100,end=10.60.1.199 --gateway=10.60.1.1 oc_provisioning-seg1 openstack subnet create --network-segment segment2 --network oc_provisioning --subnet-range 10.60.2.0/24 --dhcp --allocation-pool start=10.60.2.100,end=10.60.2.199 --gateway=10.60.2.1 oc_provisioning-seg2 openstack network segment delete segment0 # <--- deleting and recreating that broken segment brings back the dhcp IPs openstack network segment create --network oc_provisioning --physical-network provider0 --network-type flat segment0 openstack subnet create --network-segment segment0 --network oc_provisioning --subnet-range 10.60.0.0/24 --dhcp --allocation-pool start=10.60.0.100,end=10.60.0.199 --gateway=10.60.0.1 oc_provisioning-seg0 After running the second script I get all the network segments with it's dhcp ip created properly: (ironicovn-central) [stack@ironic-ovn-undercloud scripts]$ openstack port list --network oc_provisioning --device-owner network:dhcp -c "Fixed IP Addresses" -c "ID" +----------------------------------------------------------------------------+--------------------------------------+ | Fixed IP Addresses | ID | +----------------------------------------------------------------------------+--------------------------------------+ | ip_address='10.60.0.102', subnet_id='a4b8db62-50a7-47c5-a6d5-22253a19742c' | 347c5908-f867-4254-a5d3-6ec5b764ed05 | | ip_address='10.60.0.101', subnet_id='a4b8db62-50a7-47c5-a6d5-22253a19742c' | 459f1e6a-1318-42d5-877b-909150334ff0 | | ip_address='10.60.1.101', subnet_id='cb827bc1-c055-477d-8956-ad14293b0dbb' | 80f1a603-2705-42ad-bb1e-e8df03c1e3c7 | | ip_address='10.60.0.103', subnet_id='a4b8db62-50a7-47c5-a6d5-22253a19742c' | 934a9bad-0117-47e5-a605-537e83ab95e4 | | ip_address='10.60.1.100', subnet_id='cb827bc1-c055-477d-8956-ad14293b0dbb' | | | ip_address='10.60.2.101', subnet_id='6516265f-e3c1-4598-ba7c-353fdeced9d2' | | | ip_address='10.60.0.100', subnet_id='a4b8db62-50a7-47c5-a6d5-22253a19742c' | 9d3ff2a4-6d92-4cff-89ce-c258f8ae360b | | ip_address='10.60.2.100', subnet_id='6516265f-e3c1-4598-ba7c-353fdeced9d2' | ade2303d-d1c0-4a7a-8188-9d389b59d801 | | ip_address='10.60.1.103', subnet_id='cb827bc1-c055-477d-8956-ad14293b0dbb' | c5af59b6-7150-4479-b2dd-668238b8ddaa | | ip_address='10.60.1.102', subnet_id='cb827bc1-c055-477d-8956-ad14293b0dbb' | de72c40a-be9a-48de-8131-7f79d0865d2e | +----------------------------------------------------------------------------+--------------------------------------+ According to our records, this should be resolved by python-networking-ovn-7.4.2-2.20210601204831.el8ost.13. This build is available now. |