Bug 1204466
Summary: | migration failed "Error creating the requested VM" | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Eldad Marciano <emarcian> |
Component: | vdsm | Assignee: | Martin Polednik <mpoledni> |
Status: | CLOSED NOTABUG | QA Contact: | Ilanit Stein <istein> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.5.1 | CC: | bazulay, ecohen, gklein, lpeer, lsurette, michal.skrivanek, ofrenkel, rmcswain, yeylon |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | 3.5.5 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-21 13:22:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eldad Marciano
2015-03-22 12:14:00 UTC
looks like it's related to the following domain issue, at the destination host vdsm complain about this one: Thread-143359::ERROR::2015-03-22 12:17:43,116::vm::2325::vm.Vm::(_startUnderlyingVm) vmId=`859b7ddc-9f7e-47ae-9a5d-cd8aa75ffbeb`::Failed to start a migration destination vm Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 2298, in _startUnderlyingVm self._completeIncomingMigration() File "/usr/share/vdsm/virt/vm.py", line 4107, in _completeIncomingMigration self._incomingMigrationFinished.isSet(), usedTimeout) File "/usr/share/vdsm/virt/vm.py", line 4160, in _attachLibvirtDomainAfterMigration raise MigrationError(e.get_error_message()) MigrationError: Domain not found: no domain with matching uuid '859b7ddc-9f7e-47ae-9a5d-cd8aa75ffbeb' Customer has found that with "RHEV Hypervisor - 6.6 - 20150128.0.el6ev" and vdsm-4.16.8.1-6.el6ev that these migration failures continue. He has also installed a host with RHEL 6.6 containing vdsm-4.16.8.1-8.el6ev, and this seems to allow them to migrate without issues. If we can get a new RHEV-H release, this would be ideal from what we're seeing here. note: keyerror from original description fixed by f98010f311f6c223881320240217838b45c84f48, not related to the problem without logs and based on the provided information it looks like the destination simply timed out to create VM. The timeout typically happens due to slow path prepare...which is not suprising in loaded environment. Destination logs would be needed to be 100% sure. All other reported errors in vdsm log are harmless |