Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
If VM migration fails on source host, then on destination host the destroy VM fails with AttributeError: 'NetworkInterfaceDevice' object has no attribute 'name'
Created attachment 629313[details]
vdsm log
Description of problem:
If VM migration from one host to another fails for some reason on host, then on destination host the destroy VM fails with Attribute error - object has no attribute name
Steps to Reproduce:
1. Create VM on RHEVH with NET_A (not required network)
2. Create VM on RHEL with NET_B (not required network)
3. Perform migration
Actual results:
On the destination VM destroy fails with attribute error
Additional info:
This error happened when performing upgrade of DC from 3.0 to 3.1 and then for some reason VM migration started to happen and failed
Thread-14799::DEBUG::2012-10-16 17:29:20,924::BindingXMLRPC::874::vds::(wrapper) client [10.35.70.2]::call vmDestroy with ('51037cbc-7c54-4b21-9243-f085404a7f53',) {}
Thread-14799::INFO::2012-10-16 17:29:20,924::API::301::vds::(destroy) vmContainerLock acquired by vm 51037cbc-7c54-4b21-9243-f085404a7f53
Thread-14799::DEBUG::2012-10-16 17:29:20,924::libvirtvm::2152::vm.Vm::(destroy) vmId=`51037cbc-7c54-4b21-9243-f085404a7f53`::destroy Called
Thread-14799::ERROR::2012-10-16 17:29:20,925::BindingXMLRPC::892::vds::(wrapper) unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/BindingXMLRPC.py", line 879, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/BindingXMLRPC.py", line 204, in vmDestroy
return vm.destroy()
File "/usr/share/vdsm/API.py", line 306, in destroy
res = v.destroy()
File "/usr/share/vdsm/libvirtvm.py", line 2157, in destroy
response = self.releaseVm()
File "/usr/share/vdsm/libvirtvm.py", line 2095, in releaseVm
supervdsm.getProxy().unsetPortMirroring(network, nic.name)
AttributeError: 'NetworkInterfaceDevice' object has no attribute 'name'
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2012-1508.html
Created attachment 629313 [details] vdsm log Description of problem: If VM migration from one host to another fails for some reason on host, then on destination host the destroy VM fails with Attribute error - object has no attribute name Steps to Reproduce: 1. Create VM on RHEVH with NET_A (not required network) 2. Create VM on RHEL with NET_B (not required network) 3. Perform migration Actual results: On the destination VM destroy fails with attribute error Additional info: This error happened when performing upgrade of DC from 3.0 to 3.1 and then for some reason VM migration started to happen and failed