Red Hat Bugzilla – 855924 – 3.1: vdsm: vm's fail to migrate from host with vdsm-4.9.6-32 to host with vdsm-4.9-113.3 due to KeyError: 'domainID' (cluster level still 3.0)
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.
In versions of VDSM prior to 4.9-113.3, floppy and CD drives were treated as special drives. Starting with VDSM 3.9-113.3, floppy and CD drives were grouped with other drives. This difference prevented virtual machines from migrating between hosts with VDSM versions prior to and after 4.9-113.3.
VDSM was patched to allow migrations between hosts with different versions of VDSM.
Created attachment 611475[details]
logs
Description of problem:
trying to migrate a vm that started on vdsm-4.9.6-32 to host with vdsm-4.9-113.3 due to KeyError: 'domainID'
cluster level is still 3.0
Version-Release number of selected component (if applicable):
si17
vdsm-4.9.6-32.0.el6_3.x86_64
vdsm-4.9-113.3.el6_3.x86_64
How reproducible:
100%
Steps to Reproduce:
1. create a cluster 3.0, one host with vdsm 113 and one with vdsm 4.9.6
2. run vm on vdsm 4.9.6
3. migrate the vm
Actual results:
we fail migration with KeyError: 'domainID'
Expected results:
we should succeed migrate
Additional info:logs
Thread-10040::ERROR::2012-09-10 18:13:58,618::vm::382::vm.Vm::(_startUnderlyingVm) vmId=`9d1d5017-72ca-4c7c-9f66-bf9fdfce9419`::The vm start process failed
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 348, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/libvirtvm.py", line 1068, in _run
self.preparePaths()
File "/usr/share/vdsm/vm.py", line 423, in preparePaths
drive['path'] = self._prepareVolumePath(drive)
File "/usr/share/vdsm/vm.py", line 393, in _prepareVolumePath
volPath = self.cif._prepareVolumePath(drive)
File "/usr/share/vdsm/clientIF.py", line 541, in _prepareVolumePath
res = self.irs.prepareVolume(drive['domainID'], drive['poolID'],
KeyError: 'domainID'
Thread-10040::DEBUG::2012-09-10 18:13:58,626::vm::742::vm.Vm::(setDownStatus) vmId=`9d1d5017-72ca-4c7c-9f66-bf9fdfce9419`::Changed state to Down: 'domainID'
Dummy-84::DEBUG::2012-09-10 18:13:59,219::storage_mailbox::623::Storage.Misc.excCmd::(_checkForMail) 'dd if=/rhev/data-center/854f5121-8550-4582-bb73-fce7d57a569c/mastersd/dom_md/inbox iflag=direct,fullblock count=1 bs=1024000' (cwd Non
e)
FailedQA - ic158.1 & vdsm-4.9.6-40 (20121101.0.el6_3)
Same message in the WPF.
be log:
2012-11-05 09:06:28,219 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-84) Rerun vm a4201d8e-ad83-48a8-b420-d7680e3601f9. Called from vds srh-01.rhev.lab.eng.brq.redhat.com
vdsm:
Thread-138346::DEBUG::2012-11-05 08:06:26,104::task::978::TaskManager.Task::(_decref) Task=`67489e6e-bfbc-4ad6-b414-3155355945d5`::ref 0 aborting False
Thread-138315::ERROR::2012-11-05 08:06:26,449::vm::179::vm.Vm::(_recover) vmId=`a4201d8e-ad83-48a8-b420-d7680e3601f9`::migration destination error: Error creating the requested virtual machine
Thread-138315::ERROR::2012-11-05 08:06:26,512::vm::262::vm.Vm::(run) vmId=`a4201d8e-ad83-48a8-b420-d7680e3601f9`::Failed to migrate
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 245, in run
File "/usr/share/vdsm/libvirtvm.py", line 447, in _startUnderlyingMigration
RuntimeError: migration destination error: Error creating the requested virtual machine
Thread-138348::DEBUG::2012-11-05 08:06:28,160::task::588::TaskManager.Task::(_updateState) Task=`887240ad-9430-41a1-8363-9c715de179fe`::moving from state init -> state preparing
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 611475 [details] logs Description of problem: trying to migrate a vm that started on vdsm-4.9.6-32 to host with vdsm-4.9-113.3 due to KeyError: 'domainID' cluster level is still 3.0 Version-Release number of selected component (if applicable): si17 vdsm-4.9.6-32.0.el6_3.x86_64 vdsm-4.9-113.3.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: 1. create a cluster 3.0, one host with vdsm 113 and one with vdsm 4.9.6 2. run vm on vdsm 4.9.6 3. migrate the vm Actual results: we fail migration with KeyError: 'domainID' Expected results: we should succeed migrate Additional info:logs Thread-10040::ERROR::2012-09-10 18:13:58,618::vm::382::vm.Vm::(_startUnderlyingVm) vmId=`9d1d5017-72ca-4c7c-9f66-bf9fdfce9419`::The vm start process failed Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 348, in _startUnderlyingVm self._run() File "/usr/share/vdsm/libvirtvm.py", line 1068, in _run self.preparePaths() File "/usr/share/vdsm/vm.py", line 423, in preparePaths drive['path'] = self._prepareVolumePath(drive) File "/usr/share/vdsm/vm.py", line 393, in _prepareVolumePath volPath = self.cif._prepareVolumePath(drive) File "/usr/share/vdsm/clientIF.py", line 541, in _prepareVolumePath res = self.irs.prepareVolume(drive['domainID'], drive['poolID'], KeyError: 'domainID' Thread-10040::DEBUG::2012-09-10 18:13:58,626::vm::742::vm.Vm::(setDownStatus) vmId=`9d1d5017-72ca-4c7c-9f66-bf9fdfce9419`::Changed state to Down: 'domainID' Dummy-84::DEBUG::2012-09-10 18:13:59,219::storage_mailbox::623::Storage.Misc.excCmd::(_checkForMail) 'dd if=/rhev/data-center/854f5121-8550-4582-bb73-fce7d57a569c/mastersd/dom_md/inbox iflag=direct,fullblock count=1 bs=1024000' (cwd Non e)