CLOUDSTACK-8829 : Consecutive cold migration fails. - #2056
Conversation
|
Hi @borisstoyanov Bhai, |
|
@priyankparihar I can trigger smoketests for that. |
|
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-684 |
|
@blueorangutan test centos7 vmware5.5u3 |
|
@borisstoyanov unsupported parameters provided. Supported mgmt server os are: |
|
@blueorangutan test centos7 vmware-55u3 |
|
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests |
|
Trillian test result (tid-1044)
|
borisstoyanov
left a comment
There was a problem hiding this comment.
the virtio test failures will be fixed in a separate FR
sateesh-chodapuneedi
left a comment
There was a problem hiding this comment.
LGTM for code changes.
| } catch (final Exception e) { | ||
| throw new CloudRuntimeException("Failed to unregister VM: " + vm.getInstanceName() + " from source host: " + srcHost.getId() + | ||
| _agentMgr.send(srcHostId, uvc); | ||
| } catch (final AgentUnavailableException | OperationTimedoutException e) { |
ebe414e to
88b0459
Compare
Issue - Consecutive VM cold migration fails.
Root Cause Analysis - In case of VMware, if VM is being cold migrated between clusters belonging to two different VMware DCs, Cloudstack unregisters the VM from the source host and cleans up the associated VM files. The check if a VM is being cold migrated across DCs is made using the source host id. In case of consecutive cold migrations since the source host id of a VM is NULL and no VM exists, Cloudstack should skip the check
Proposed Solution - Attempt to unregister a VM in another DC, only if there is a host associated with a VM.
This closes #797