Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1809344

Summary:	OVN MTU changes not propagated to subnet DHCP_Options
Product:	Red Hat OpenStack	Reporter:	chrisbro <chrisbro>
Component:	openvswitch	Assignee:	Open vSwitch development team <ovs-team>
Status:	CLOSED DUPLICATE	QA Contact:	Eran Kuris <ekuris>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	apevec, chrisw, jlibosva, rhos-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-03 14:28:17 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 chrisbro@redhat.com 2020-03-02 21:52:56 UTC

Description of problem:

OVN MTU changes not propagated to subnet DHCP_Options

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.This relates to this upstream bug: https://bugs.launchpad.net/networking-ovn/+bug/1816449
2.
3.

Actual results:


Expected results:


Additional info:

When the MTU is set on a Neutron network in OVN the change is not promulgated to the DHCP_Options the NB DB.

This was fixed upstream and appears to have been placed into Rocky and Stein, but is not available in Queens.

The workaround is to disable and then re-enable DHCP on the affected subnets, thereby clearing and re-adding the required row in DHCP_Options.

Comment 2 Jakub Libosvar 2020-03-03 14:28:17 UTC


*** This bug has been marked as a duplicate of bug 1685634 ***