Bug 2022354

Summary:	Network gateway stays out-of-sync after upgrade
Product:	[oVirt] vdsm	Reporter:	Ales Musil <amusil>
Component:	Core	Assignee:	Ales Musil <amusil>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.40.80	CC:	bugs, mkalinin, mperina
Target Milestone:	ovirt-4.4.10	Keywords:	ZStream
Target Release:	4.40.100.1	Flags:	mperina: ovirt-4.4+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdsm-4.40.100.1-1.el8ev.x86_64	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-19 07:00:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ales Musil 2021-11-11 12:40:36 UTC

Description of problem:
After update to use nmstate source routes the code won't create 
a new source route unless the config has changed. This however might not be 
the case if the routes for example removed externally, in that case
the network configuration would stay the same but the route is missing. 
That causes out-of-sync on engine that cannot be fixed by simple network synchronization. 

Version-Release number of selected component (if applicable):
vdsm-4.40.80.6-1.el8ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Setup network with custom gateway (static/dynamic) that is not default route
2. Remove the source route from host 
3. try to synchronize the network on the host


Actual results:
Engine shows the network is still out-of-sync, missing the gateway

Expected results:
It should be synchronized

Additional info:
There are two possible workarounds:
1) Change or remove the gateway of affected network, apply the configuration to the host and then apply the configuration again with the gateway back. 
2) Remove /var/lib/vdsm/staging/netconf/nets/$NET_NAME on the host and then run network synchronization from engine

Comment 1 Ales Musil 2021-11-11 13:21:36 UTC

One small thing to note, this does not apply to networks that have default route role.

Comment 3 Michael Burman 2021-11-22 12:35:32 UTC

Verified on - vdsm-4.40.100.1-1.el8ev.x86_64 with rhvm-4.4.10-0.17.el8ev.noarch

Comment 4 Sandro Bonazzola 2022-01-19 07:00:13 UTC

This bugzilla is included in oVirt 4.4.10 release, published on January 18th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.4.10 release, it has been closed with a resolution of CURRENT RELEASE.

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