This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2317638 - [ovn migration] - dhcp agent port cleanup
Summary: [ovn migration] - dhcp agent port cleanup
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 17.1 (Wallaby)
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: z5
: 17.1
Assignee: Jakub Libosvar
QA Contact: Bernard Cafarelli
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-09 17:21 UTC by Matt Flusche
Modified: 2025-01-10 10:21 UTC (History)
9 users (show)

Fixed In Version: openstack-neutron-18.6.1-17.1.20241119170903.85ff760.el9osttrunk
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-01-10 10:19:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   OSP-32929 0 None None None 2025-01-10 10:19:36 UTC
Red Hat Issue Tracker OSP-33406 0 None None None 2025-01-10 10:21:00 UTC

Description Matt Flusche 2024-10-09 17:21:18 UTC 
Description of problem:

In a standard ML2/OVS deployment there are 3 dhcp agents per network, each using a port.  When converting to OVN a new port is created for OVN internal dhcp.  After OVS->OVN migration there are 4 dhcp ports allocated.  For most situations only the internal OVN dhcp port (labeled "distributed") is needed after.

In the migration ansible, I see cleanup code for dhcp- agent namespaces and services.  Should these clean-up tasks remove the dhcp agent ports?  or is additional instructions needed to fully cleanup/purge dhcp agents after migration.



Version-Release number of selected component (if applicable):
17.1
Note You need to log in before you can comment on or make changes to this bug.