Bug 1230775

Summary: Engine should block run of vm with network-used host devices.
Product: [oVirt] ovirt-engine Reporter: Martin Betak <mbetak>
Component: GeneralAssignee: Martin Betak <mbetak>
Status: CLOSED CURRENTRELEASE QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: bugs, gklein, lsurette, mbetak, mburman, michal.skrivanek, rbalakri, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcFlags: rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.6.0-12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 12:55:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Martin Betak 2015-06-11 14:12:58 UTC 
Description of problem: 

It is currently possible to run a VM with passed-through device that is used by a VLAN or logical network which can result in loss of connectivity to the host. 

The engine should detect such situations and prevent run of VM where any required host device is occupied for networking purpose.
Comment 1 Michael Burman 2016-01-21 11:14:45 UTC 
Hi Martin,

Please explain how to test this report with exact steps, thank you.
Comment 2 Martin Betak 2016-02-01 09:29:26 UTC 
Hi Michael,

the simplest scenario to verify this would be to:

1) have a vm pinned to a host
2) attach to VM host device representing host's NIC that is used with the ovirtmgmt network.
3) Try to run this VM
4) VM Run should fail becouse its device is not available (since it is used for ovirtmgmt and dettaching it from host for passthrough purposes would make the host non-responsive)

Hope that helps.

Best regards,

Martin
Comment 3 Michael Burman 2016-02-02 07:27:00 UTC 
Hi Martin)

This report was tested with success on 3.6.3-0.1.el6 and can be verified - engine blocking run of VM with host device that has a network attached to him, but the error message is not clear and should be improved -->

"Error while executing action: 

sr-vm3:
Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:
The host puma22.scl.lab.tlv.redhat.com did not satisfy internal filter HostDevice because some of the required host devices are unavailable.."

The error message should explain that the host devices are unavailable because they are in use by some network/s or something like that. Agree?
Comment 4 Michael Burman 2016-02-02 07:28:56 UTC 
Created attachment 1120345 [details]
screenshot
Comment 5 Martin Betak 2016-02-02 10:52:29 UTC 
Hi Michael,

You are right the error message deserves much improvement and we are want to improve the error reporting capabilities for the HostDev 2.0 phase scheduled to land in 4.0 - as a part of bigger extension/redesign of the current host dev feature.

Best regards,

Martin
Comment 6 Michael Burman 2016-02-02 11:27:02 UTC 
Verified on - 3.6.3-0.1.el6