Bug 1397507 - [RFE] engine should check the state of VIF driver installed on host
Summary: [RFE] engine should check the state of VIF driver installed on host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: future
Hardware: x86_64
OS: Linux
medium
medium vote
Target Milestone: ovirt-4.3.0
: ---
Assignee: Yaniv Lavi
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-22 16:34 UTC by Mor
Modified: 2018-04-04 08:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-04 08:23:23 UTC
oVirt Team: Network
ylavi: ovirt-4.3?
mkalfon: planning_ack?
mkalfon: devel_ack?
mkalfon: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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