Bug 2062645

Summary:	configure-ovs: don't restart networking if not necessary
Product:	OpenShift Container Platform	Reporter:	Jaime Caamaño Ruiz <jcaamano>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	ovn-kubernetes	QA Contact:	Ross Brattain <rbrattai>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	rbrattai
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
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:	2022-08-10 10:53:13 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:
Bug Depends On:
Bug Blocks:	2062666

Description Jaime Caamaño Ruiz 2022-03-10 10:05:58 UTC

Description of problem:

configure-ovs restarts networking unconditionally even if no configuration changes where introduced. This adds a delay on boot and introduces a new vector of possible problems that is really not necessary when no configuration changes were made.


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


How reproducible:
always

Expected results:
configure-ovs should only restart networking if any configuration changes were made

Comment 3 Ross Brattain 2022-03-24 17:47:43 UTC

Verified on 4.11.0-0.nightly-2022-03-20-160505  

rebooted node to also check `rollback_nm`

Comment 5 errata-xmlrpc 2022-08-10 10:53:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069