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

Bug 1539576

Summary:	ovn localnet - Engine should schedule VMs only on hosts where phys_net is attached
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	Ales Musil <amusil>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.1.2	CC:	bugs, danken
Target Milestone:	ovirt-4.3.0	Flags:	rule-engine: ovirt-4.3+ mburman: testing_plan_complete- mburman: testing_ack+
Target Release:	4.3.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.0_alpha	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 07:48:06 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 Michael Burman 2018-01-29 08:53:55 UTC

Description of problem:
ovn localnet - Engine should scheduled VMs only on hosts where phys_net is attached.

Engine should schedule and run VMs only on hosts with phys_net attached networks, if there is no available host, VM shouldn't start. 
This behaviour is only(and will be) relevant for OVS type clusters. 

Currently VM can run when the underlying phys_net is not attached to the host.

Version-Release number of selected component (if applicable):
4.2.1.3-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1. Create phys_net with vlan and don't attach to host in OVS type cluster
2. Create ovn network on external provider(via UI) + select the phys_net from data center networks
3. Run VM 

Actual results:
VM started

Expected results:
VM shouldn't run. There shouldn't be available host for this VM as it has no phys_net attached to the host

Comment 1 Michael Burman 2018-08-21 11:55:55 UTC

Verified on - 4.3.0-0.0.master.20180819104048.git932969e.el7 with vdsm-4.30.0-531.git26b1bd3.el7.x86_64

Comment 2 Sandro Bonazzola 2018-11-02 14:31:04 UTC

This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 3 Sandro Bonazzola 2018-11-02 14:51:38 UTC

Closed by mistake, moving back to qa -> verified

Comment 4 Sandro Bonazzola 2019-02-13 07:48:06 UTC

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.