Bug 1397507

Summary:	[RFE] engine should check the state of VIF driver installed on host
Product:	[oVirt] ovirt-engine	Reporter:	Mor <mkalfon>
Component:	RFEs	Assignee:	Yaniv Lavi <ylavi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Gil Klein <gklein>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	future	CC:	bugs, danken, ylavi
Target Milestone:	ovirt-4.3.0	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-4.3? mkalfon: planning_ack? mkalfon: devel_ack? mkalfon: testing_ack?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-04 08:23:23 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:

Description Mor 2016-11-22 16:34:08 UTC

Description of problem:
Running a VM attached to OVN network on non OVN-controller host shows generic error: “Cannot get interface MTU on: <net> no such device”. 

The root cause is that the engine is not aware if a host has an external VIF installed and ready for usage. Maybe we can approach this by adding a new host capability?


Version-Release number of selected component (if applicable):
oVirt Engine Version: 4.1.0-0.0.master.20161120231325.gitba51756.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Create VM with OVN network attached to it.
2. Try to run a VM on a non OVN-controller host.

Actual results:
generic error: “Cannot get interface MTU on: <net> no such device”

Expected results:
Engine should block us for doing such thing.

Additional info:

Comment 1 Yaniv Lavi 2018-04-04 08:23:23 UTC

We install OVN on host deploy, if that fails the host deploy fails, so this is not needed.