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
Verified on - 4.3.0-0.0.master.20180819104048.git932969e.el7 with vdsm-4.30.0-531.git26b1bd3.el7.x86_64
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.
Closed by mistake, moving back to qa -> verified
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.