Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 6 Jul 2017 10:34:04 +0000 (UTC)
From: "Rajani Karuturi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13058769.1490314513000.183458.1499337244859@Atlassian.JIRA>
In-Reply-To: <JIRA.13058769.1490314513000@Atlassian.JIRA>
References: <JIRA.13058769.1490314513000@Atlassian.JIRA> <JIRA.13058769.1490314513178@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CLOUDSTACK-9849) Cannot migrate VMware VM to host
 in different cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 06 Jul 2017 10:34:19 -0000


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajani Karuturi updated CLOUDSTACK-9849:
----------------------------------------
    Fix Version/s:     (was: 4.10.0.0)
                   4.10.1.0

> Cannot migrate VMware VM to host in different cluster
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-9849
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9849
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.10.0.0
>         Environment: VMware 5.5
>            Reporter: Mike Tutkowski
>            Assignee: Sateesh Chodapuneedi
>             Fix For: 4.10.1.0
>
>
> I have two VMware clusters in the same VMware datacenter. Each cluster has a single ESXi 5.5 host in it.
> I have a shared primary storage in each cluster (I have tried this scenario with both NFS and iSCSI shared primary storage and the results are the same).
> I have a VM with its root disk running on primary storage from a host in the one cluster and I cannot migrate this VM and its root disk to the host in the other cluster (both primary storages even make use of the same storage tag).
> The source host has access to the source datastore, but it does not have access to the target datastore.
> The target host has access to the target datastore, but it does not have access to the source datastore.
> When I try to perform the migration, it fails with the following error message:
> Required property datastore is missing from data object of type VirtualMachineRelocateSpecDiskLocator
> while parsing serialized DataObject of type vim.vm.RelocateSpec.DiskLocator
> at line 1, column 327
> while parsing property "disk" of static type ArrayOfVirtualMachineRelocateSpecDiskLocator
> while parsing serialized DataObject of type vim.vm.RelocateSpec
> at line 1, column 187
> while parsing call information for method RelocateVM_Task
> at line 1, column 110
> while parsing SOAP body
> at line 1, column 102
> while parsing SOAP envelope
> at line 1, column 38
> while parsing HTTP request for method relocate
> on object of type vim.VirtualMachine
> at line 1, column 0
> When I run the test in the debugger and look at the VirtualMachineRelocateSpec instance passed to VirtualMachineMO.changeDatastore, I see the target datastore is populated, but not the source datastore:
> http://imgur.com/a/vtKcq datastore-66 is the target datastore
> Based on an e-mail chain on dev@, it sounds like my scenario should work.
> Thanks!


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)