Bug 1132951

Summary:	uninformative engine error message when trying to start/create vm and display network has no ip
Product:	[Retired] oVirt	Reporter:	Sven Kieske <s.kieske>
Component:	ovirt-engine-core	Assignee:	Martin Sivák <msivak>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Meni Yakove <myakove>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3	CC:	bazulay, bugs, ecohen, gcheresh, gklein, mburman, msivak, oourfali, rbalakri, yeylon
Target Milestone:	---
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:	2015-11-04 11:36:32 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 Sven Kieske 2014-08-22 12:33:38 UTC

Description of problem:
1. when your display network has no ip address assigned
and you try to start an existing vm you get a libvirt error:
"vnet0 not in keymap" this is not very helpful, even for admins
in getting the core error.
the vm does not start (I wonder if this is even necessary, you could
live without any graphic way to access the vm, e.g. accessing your vms directly via network)

2. when you want to create a new vm without display network ip
you can't hit the "ok" button in the gui without any indication what
is wrong at all.
Version-Release number of selected component (if applicable):
3.3.3, not sure if this still occurs in master/3.5/3.4 branch, please check yourself

How reproducible:
always

Steps to Reproduce:
1. remove ip from display network
2. try to start vm / try to create a vm
3. watch libvirt error in events // you can't click "ok" in the create vm dialog


Actual results:
can't start vm// can't create vm

Expected results:
can start vm// can create vm
or at least get a clear error message like:
"error: could not start vm: your display network has no IP configured"

Additional info:

please verify if this still occurs in ovirt 3.4.z and 3.5 RC
I can't test it atm, maybe this is already fixed in 3.4 and/or 3.5

please let me know, this could be the last needed fix to encourage me to
finally upgrade ;)

Comment 1 Oved Ourfali 2014-08-25 12:07:23 UTC

assigning to network team to have a look. Might move to virt later, I guess.

Comment 2 GenadiC 2014-08-31 12:08:25 UTC

Trying to start VM in 3.5 when display network has no ip you get "The host <host_name> did not satisfy internal filter Network because network(s) are missing."
But networks are not missing you just didn't configure IP on the display network

Comment 3 Lior Vernia 2014-08-31 12:21:38 UTC

Martin,

Didn't you improve the error of the article (1) scenario in master a while ago? If so, could you please backport the patch to 3.5?

By the way, article (2) in the description doesn't make sense to me - it should be possible to create/edit a VM with no relation to the display network, the problem is only with running it. I suspect there was a different error in the dialog.

Comment 4 Lior Vernia 2014-09-02 13:13:30 UTC

I referred to Bug 1114987, adding tracker for the patch pushed in that context.

Comment 5 Sven Kieske 2014-09-22 09:16:30 UTC

I'm a little puzzled.

I just stumbled upon BZ 955429

according to this BZ this should be already fixed?

Or is this just fixed for rhev and not for ovirt?

Comment 6 Martin Sivák 2014-09-22 09:57:32 UTC

Sven:

The fix you are referencing was fixed for 3.4 (both oVirt and RHEV) and was not backported to 3.3:

http://gerrit.ovirt.org/#/q/I14e5a0edae8524a7334609e58934880a722ca87f,n,z
https://bugzilla.redhat.com/show_bug.cgi?id=955429

GenadiC:

That is a different bug as Lior pointed out: https://bugzilla.redhat.com/show_bug.cgi?id=1114987


Guys, the original report looks like DUP to me and then Lior with GenadiC confused things by adding another issue to it (which would make this a DUP as well).

Comment 7 Lior Vernia 2014-09-22 10:09:41 UTC

Bug 955429 was about adding a check whether the display network has an IP address, and if not fail the the running of a VM.

Bug 1114987 caused hosts to falsely report that their interfaces have no boot protocol when they had DHCP configured, which caused your original issues when running VMs.

The only thing left to fix in this bug is to improve the error message in case of a failure due to the display network. This is no confusion - it is consistent with the title of this bug, and as Sven mentioned:

<snip>
"vnet0 not in keymap" this is not very helpful, even for admins
in getting the core error.
</snip>

I don't know if this is still the message shown today, but the message shown today definitely doesn't give any information about the display network not having boot protocol, and it's hard to debug.

I'm not aware of any bug this should be a duplicate of.

Comment 8 Martin Sivák 2014-09-22 10:31:02 UTC

This bug is about libvirt message that was imho removed by fixing Bug 955429. Not scheduling message. Those two are not related in any way.

Comment 9 Lior Vernia 2014-09-22 10:33:09 UTC

Done.

Comment 10 Michael Burman 2015-04-27 08:40:40 UTC

Verified on - 3.6.0-0.0.master.20150412172306.git55ba764.el6


Operation Canceled

Error while executing action:

micbu:

    Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:
    The host navy-vds3.qa.lab.tlv.redhat.com did not satisfy internal filter Network because the display network mbmb must have a DHCP or Static boot protocol when configured on a host.

- This error message is very specific and makes it very clear to understand that the problem is with the display network configuration on host.

Comment 11 Sandro Bonazzola 2015-11-04 11:36:32 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.