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

Bug 1135779

Summary:	Display network should be required
Product:	[Retired] oVirt	Reporter:	GenadiC <gcheresh>
Component:	ovirt-engine-core	Assignee:	Lior Vernia <lvernia>
Status:	CLOSED NOTABUG	QA Contact:	GenadiC <gcheresh>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5	CC:	acathrow, bazulay, bugs, danken, ecohen, gklein, iheim, mgoldboi, myakove, yeylon
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	3.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-22 09:01:41 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 GenadiC 2014-08-31 13:30:03 UTC

Description of problem:
If you create a network as non-required, you should be unable to choose it as a display network for your cluster

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


How reproducible:
Always

Steps to Reproduce:
1. Create network as non-required
2. Choose this network as display network in Cluster/manage networks tab
3.

Actual results:
An action succeeds

Expected results:
An action should fail, it should succeed only when you change the network to be required

Additional info:

Comment 1 Dan Kenigsberg 2014-09-06 22:33:22 UTC

It cannot be said categorically that the display network of a VM is more important than its VM network. If you are running a multi-vm DB server, and you need to spawn a new instance to serve a surge in requirement, you care much less about the display network of the VM. If there's a host lacks the display network, but has all functionally-required networks, the VM should start up there.

Let us not nanny the user. If he declared the network as non-required, he probably means just that - it's nice to have the network in his use case, but it's not the end of the world if it's not there.

Comment 2 Lior Vernia 2014-09-14 10:32:30 UTC

While I agree that in the long term we should allow running VMs without a display network, I'm unaware of such an RFE and currently the display network behaves de-facto as a required network, so we might as well reflect that in the GUI and in the engine.

Comment 3 Dan Kenigsberg 2014-09-17 22:39:19 UTC

If a non-required network looses its connectivity, VMs that have vNICs connected to it looses their network. But nothing horrible happens; the host is still oprational, and VMs do not migrate away, since the admin defined it as non-required.

Same logic applies, and should continue to apply, when the network is connected to the virtual video device instead of a vNIC. VMs would loose their display for a while, but it's no big deal since the admin explicitly said so.

Note that we cannot (and should not) start a VM if its display network does not have an IP on that host (bug 955429). Headless VMs (lacking video card) are cool, but not immediately related to this (not)bug.

Comment 4 Lior Vernia 2014-09-22 09:01:41 UTC

Dan has made a very good point; my statement that display network behaves de-facto as a required network was inaccurate. A difference in behavior would be in the case of a display NIC going down while VMs are running on the host - if the network is required the VMs will be migrated away, while if it isn't they'll keep running. This is a strong enough case to allow for a non-required display network.