Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 1 Jul 2015 08:00:11 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12841598.1435650320000.68092.1435737611301@Atlassian.JIRA>
In-Reply-To: <JIRA.12841598.1435650320000@Atlassian.JIRA>
References: <JIRA.12841598.1435650320000@Atlassian.JIRA>
 <JIRA.12841598.1435650320176@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8597) Failed to migrate a volume
 from zone-wide to cluster-wide storage.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609705#comment-14609705 ] 

ASF GitHub Bot commented on CLOUDSTACK-8597:
--------------------------------------------

Github user wilderrodrigues commented on the pull request:

    https://github.com/apache/cloudstack/pull/541#issuecomment-117517309
  
    Hi @likitha 
    
    I understood what the issue says, but what I really meant concerns what the code does.
    
    The only practical change in the code was this:
    
    if (volume.getHypervisorType() == Hypervisor.HypervisorType.Hyperv || volume.getHypervisorType() == Hypervisor.HypervisorType.VMware) {
    ...
    }
    
    Which means that now it will also get in the IF when the Hypervisor is of HypervisorType.VMware type.
    
    So, what you really want is: support volume migration from zone-wide to cluster-wide storage when hypervisor is VMware.
    
    Is that correct?
    
    If you look further at the code, when CS will do DELETEVOLUME, it would take into account only VMware. So, HyperV wouldn't be supported.
    
    ![image](https://cloud.githubusercontent.com/assets/5129209/8450115/dc04f71c-1fd7-11e5-8cbc-127d4030ce73.png)
    
    Cheers,
    Wilder


> Failed to migrate a volume from zone-wide to cluster-wide storage.
> ------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8597
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8597
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>             Fix For: 4.6.0
>
>
> +Steps to reproduce+
> 1. Have 2 clusters with a host and cluster-wide storage each.
> 2. Have a zone-wide storage spanning both clusters.
> 3. Deploy a VM with a datadisk.
> 4. Ensure datadisk is on the zone-wide storage. Attempt to migrate it to the cluster-wide storage (cluster that contains the disks's VM).
> 5. Try the above operation repeatedly till a failure is seen.
> Migration may fails with the below -
> {noformat}
> 2015-06-08 14:37:00,079 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-86:ctx-b374c26e 10.102.192.12, job-192/job-193, cmd: MigrateVolumeCommand) (logid:ea70ca83) Unable to find the mounted datastore with name 23b5a868-b6af-3692-85f5-f1d987b7f3e2 to execute MigrateVolumeCommand
> 2015-06-08 14:37:00,084 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-86:ctx-b374c26e 10.102.192.12, job-192/job-193, cmd: MigrateVolumeCommand) (logid:ea70ca83) Catch Exception java.lang.Exception due to java.lang.Exception: Unable to find the mounted datastore with name 23b5a868-b6af-3692-85f5-f1d987b7f3e2 to execute MigrateVolumeCommand
> java.lang.Exception: Unable to find the mounted datastore with name 23b5a868-b6af-3692-85f5-f1d987b7f3e2 to execute MigrateVolumeCommand
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3561)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:414)
>         at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:317)
>         at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>         at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>         at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>         at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>         at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:722)
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)