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

Bug 918013

Summary: [RHEVM] [backend] [Network Linking] cannot assign non-required network which is not attached host to existing VNIC
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Pavlik <mpavlik>
Component: ovirt-engineAssignee: Alona Kaplan <alkaplan>
Status: CLOSED NOTABUG QA Contact: Martin Pavlik <mpavlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, dyasny, gklein, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-06 13:33:12 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:
Attachments:
Description Flags
sosreport-LogCollector-admin-20130305105649-a74f.tar none

Description Martin Pavlik 2013-03-05 10:03:25 UTC
Created attachment 705348 [details]
sosreport-LogCollector-admin-20130305105649-a74f.tar

Description of problem: 
It is not possible to assign existing VNIC with non-required network which is assigned to the cluster, but not to the host. It should be possible to do so, because when crating new VNIC (link down, unplugged) it works.


Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.2.0-10.10.beta1.el6ev 

How reproducible:
100%

Steps to Reproduce:
1. create new non-required logical network, attach it to the cluster, do not attach it to any host
2. create VM without VNICs, start the VM, wait until VM is UP
3. create new VNIC attached to rhevm network (plugged, link up)
4. edit the VNIC, attach it to the network created in step 1 (unplugged, link down)
  
Actual results:
ERROR:
The Network does not exist on the host the VM is running on.
Either add the Network to the Host or migrate the VM to a Host that has this Network.

Expected results:
VNIC attached to the non-required logical network which is not attached to the host

Additional info:

editing existing VNIC
013-03-05 10:48:27,406 WARN  [org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand] (ajp-/127.0.0.1:8702-3) [685f8ee4] CanDoAction of action ActivateDeactivateVmNic failed. Reasons:VAR__ACTION__DEACTIVATE,VAR__TYPE__INTERFACE,ACTIVATE_DEACTIVATE_NETWORK_NOT_IN_VDS


addning new VNIC
2013-03-05 10:50:34,001 INFO  [org.ovirt.engine.core.bll.network.vm.AddVmInterfaceCommand] (ajp-/127.0.0.1:8702-2) [3f971b60] Running command: AddVmInterfaceCommand internal: false. Entities affected :  ID: be00921f-365f-42bb-99d0-b33b4a097c1b Type: VM,  ID: 1bbfb929-8e17-4880-b660-9597698184aa Type: Network