Bug 1522971 - move defaultRoute=True to a new network even if persisted on a former network
Summary: move defaultRoute=True to a new network even if persisted on a former network
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.20.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.1
: ---
Assignee: Edward Haas
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-06 20:54 UTC by Dan Kenigsberg
Modified: 2018-02-12 11:57 UTC (History)
4 users (show)

Fixed In Version: v4.20.9-94
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-12 11:57:35 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+
ylavi: exception+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 85521 0 master MERGED net: DefaultRoute move semantic 2018-01-02 15:54:18 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.