Bug 1522971

Summary:	move defaultRoute=True to a new network even if persisted on a former network
Product:	[oVirt] vdsm	Reporter:	Dan Kenigsberg <danken>
Component:	Core	Assignee:	Edward Haas <edwardh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.20.0	CC:	bugs, edwardh, mburman, ylavi
Target Milestone:	ovirt-4.2.1	Flags:	rule-engine: ovirt-4.2+ ylavi: exception+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	v4.20.9-94	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-12 11:57:35 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 Dan Kenigsberg 2017-12-06 20:54:18 UTC

If Vdsm is asked to set defaultRoute=True where gateway is missing, Vdsm silently fails. It does not report back defaultRoute=True, but it does not allow to set it on another network before clearing it first.

Comment 1 Michael Burman 2018-01-08 09:37:05 UTC

Verified on - vdsm-4.20.11-1.el7ev.x86_64 and 4.2.1-0.2.el7

Comment 2 Sandro Bonazzola 2018-02-12 11:57:35 UTC

This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 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.