cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Likitha Shetty (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-7371) [VMware] Enabling primary storage maintenance fails when storages are across cluster
Date Tue, 19 Aug 2014 10:03:18 GMT
Likitha Shetty created CLOUDSTACK-7371:
------------------------------------------

             Summary: [VMware] Enabling primary storage maintenance fails when storages are
across cluster
                 Key: CLOUDSTACK-7371
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7371
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Storage Controller, VMware
    Affects Versions: 4.5.0
            Reporter: Likitha Shetty
            Assignee: Likitha Shetty
            Priority: Critical
             Fix For: 4.5.0


Have two primary storage across 2 clusters. Put the storage that has at least one system vm
into maintenance. The system vm will fail to start in the second storage with the following
error - 
{noformat}
2014-08-18 17:07:50,337 WARN  [c.c.h.v.r.VmwareResource] (DirectAgent-134:ctx-440166e2 10.102.192.7,
job-129/job-134, cmd: StartCommand) StartCommand failed due to Exception: java.lang.RuntimeException
Message: The name 's-2-VM' already exists.

java.lang.RuntimeException: The name 's-2-VM' already exists.
        at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:335)
        at com.cloud.hypervisor.vmware.mo.HostMO.createVm(HostMO.java:559)
        at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.createBlankVm(HypervisorHostHelper.java:1165)
        at com.cloud.hypervisor.vmware.mo.HostMO.createBlankVm(HostMO.java:744)
        at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1391)
        at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:448)
        at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
        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.run(FutureTask.java:262)
        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:744)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message