Bug 1950415 - [ovn] ML2/OVN deployments should have neutron-ovs-cleanup run upon hypervisors boot
Summary: [ovn] ML2/OVN deployments should have neutron-ovs-cleanup run upon hypervisor...
Keywords:
Status: CLOSED DUPLICATE of bug 1908638
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kamil Sambor
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-16 15:18 UTC by Daniel Alvarez Sanchez
Modified: 2022-08-23 22:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-19 12:17:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-3080 0 None None None 2022-08-23 22:45:02 UTC

Description Daniel Alvarez Sanchez 2021-04-16 15:18:09 UTC
neutron-ovs-cleanup script cleans the ports from the integration bridge and then Nova (os-vif) will plug the relevant instances ports to it.

This script doesn't run on ML2/OVN setups and it should for the same reasons it does on ML2/OVS.

Comment 1 smooney 2021-04-16 16:24:30 UTC
afctully i dont think this is correct.

even ml2/ovs should not have this run regually
we dont expect this to be run upstream it ment as a tool to help fix leaked port when we hit bugs.

this is racy to run on start up as it can interfee with nova/libvirt plugin the interface if the resume gusts on boot config option is enabled

so i would suggest disabling this for both ml2/ovs and ml2/ovn by default.


Note You need to log in before you can comment on or make changes to this bug.