Bug 999045

Summary: Changing VNIC profile to another one on the running VM fails with Unexpected exception
Product: Red Hat Enterprise Virtualization Manager Reporter: GenadiC <gcheresh>
Component: vdsmAssignee: lpeer <lpeer>
Status: CLOSED DUPLICATE QA Contact: GenadiC <gcheresh>
Severity: unspecified Docs Contact:
Priority: high    
Version: 3.3.0CC: bazulay, danken, hateya, iheim, lpeer, myakove, yeylon
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-08-27 20:51:30 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
vdsm log
none
engine log
none
supervdsm log none

Description GenadiC 2013-08-20 15:21:32 UTC 
Created attachment 788545 [details]
vdsm log

Description of problem:
Trying to change VNIC profile to another one fails with unexpected exception
Happened when changing to profile attached to the same or another network

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1. Create VM with VNIC profile A attached to network red
2. When VM is up update VM to have VNIC profile B attached to network red instead of A
3.

Actual results:


Expected results:
Action fails

Additional info:
After unplugging NIC and plugging it back the problem disappeared
The logs with the problem attached
Comment 1 GenadiC 2013-08-20 15:22:43 UTC 
Created attachment 788547 [details]
engine log
Comment 2 GenadiC 2013-08-20 15:23:38 UTC 
Created attachment 788548 [details]
supervdsm log
Comment 3 Dan Kenigsberg 2013-08-27 20:51:30 UTC 
It looks like a dup of bug 1001001 (which is a binary palindrome, so I'm keeping it open)


Thread-5668::DEBUG::2013-08-20 17:46:34,578::vm::3101::vm.Vm::(setLinkAndNetwork) vmId=`4f8378d3-b896-4947-b604-844f03b0d4e4`::Request failed: <interface type="bridge">
	<address bus="0x00" domain="0x0000" function="0x0" slot="0x04" type="pci"/>
	<mac address="00:1a:4a:16:88:6f"/>
	<model type="virtio"/>
	<source bridge="red"/>
	<filterref filter="vdsm-no-mac-spoofing"/>
	<link state="up"/>
	<boot order="2"/>
</interface>
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 3096, in setLinkAndNetwork
    libvirt.VIR_DOMAIN_AFFECT_LIVE)
  File "/usr/share/vdsm/vm.py", line 824, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 76, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1742, in updateDeviceFlags
    if ret == -1: raise libvirtError ('virDomainUpdateDeviceFlags() failed', dom=self)
libvirtError: this function is not supported by the connection driver: cannot modify network device boot index setting

*** This bug has been marked as a duplicate of bug 1001001 ***