[
https://issues.apache.org/jira/browse/CLOUDSTACK-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258132#comment-14258132
]
ASF subversion and git services commented on CLOUDSTACK-8125:
-------------------------------------------------------------
Commit 7b32b8a26808a546d1dbfdf4728c6228a41852b6 in cloudstack's branch
refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7b32b8a ]
CLOUDSTACK-8125. VM fails to start on the first attempt after a cold migration.
Update volume chain_info to NULL during cold migration.
Otherwise during VM start, CCP will configure and try to power-on the VM with
wrong disk information.
> [VMware] After cold migration of a VM, VM starts with warning messages in MS
> logs
> ---------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8125
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8125
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: Future
>
>
> +Steps to reproduce+
> 1. Deploy a vm.
> 2. Stop the VM.
> 3. Add another primary storage to the same cluster.
> 4. Migrate the VM to the new primary storage.
> 5. Try to start the VM.
> Issue - First attempt to start the VM fails with
> {noformat}
> java.lang.RuntimeException: File
> []/vmfs/volumes/27951060-bbb89fa5/i-2-10-VM/daadfb44467f41e6a38fd8ba05e28cb4.vmdk
> was not found
> {noformat}
> The VM eventually starts up but the disks are migrated back to the old
> storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
