Bug 2317638

Summary: [ovn migration] - dhcp agent port cleanup
Product: Red Hat OpenStack Reporter: Matt Flusche <mflusche>
Component: openstack-neutronAssignee: Jakub Libosvar <jlibosva>
Status: CLOSED MIGRATED QA Contact: Bernard Cafarelli <bcafarel>
Severity: high Docs Contact:
Priority: medium    
Version: 17.1 (Wallaby)CC: chrisw, dhughes, egarciar, jelle.hoylaerts.ext, kgilliga, ktordeur, mtomaska, scohen, toneata
Target Milestone: z5Keywords: Triaged
Target Release: 17.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-neutron-18.6.1-17.1.20241119170903.85ff760.el9osttrunk Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-01-10 10:19:37 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 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