cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-7662) [VMware] Resize of detached volumes fails
Date Wed, 01 Oct 2014 10:24:34 GMT


ASF subversion and git services commented on CLOUDSTACK-7662:

Commit 65ed25b7a63586e25a568d845527d547f0045889 in cloudstack's branch refs/heads/master from
[;h=65ed25b ]

BUG-ID: CLOUDSTACK-7662. Resize of detached volume fails.
Support offline volume resize on ESX by creating a worker VM to attach the unattached volume
to and then resize it.

> [VMware] Resize of detached volumes fails
> -----------------------------------------
>                 Key: CLOUDSTACK-7662
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware, Volumes
>    Affects Versions: 4.5.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.5.0
> +Problem+
> Resize of detached volumes fails with the following error
> {noformat}
> INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-9:ctx-39d10699 job-4056) Add job-4056
into job monitoring 
> ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-103:ctx-145f612d
VM none does not exist in VMware datacenter 
> ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-103:ctx-145f612d
Unable to resize volume 
> java.lang.Exception: VM none does not exist in VMware datacenter 
> at

> at

> at$Task.runInContext(

> at org.apache.cloudstack.managed.context.ManagedContextRunnable$

> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$

> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(

> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(

> at

> at java.util.concurrent.Executors$ 
> at java.util.concurrent.FutureTask$Sync.innerRun( 
> at 
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(

> at java.util.concurrent.ScheduledThreadPoolExecutor$

> at java.util.concurrent.ThreadPoolExecutor.runWorker( 
> at java.util.concurrent.ThreadPoolExecutor$ 
> at 
> WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl] (API-Job-Executor-9:ctx-39d10699 job-4056
ctx-b2cc315e) Unsupported data object (VOLUME,,
no need to delete from object in store ref table 
> WARN [c.c.s.VolumeApiServiceImpl] (API-Job-Executor-9:ctx-39d10699 job-4056 ctx-b2cc315e)
Failed to resize the volume Vol[225|vm=null|DATADISK] 
> INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-9:ctx-39d10699 job-4056) Remove
job-4056 from job monitoring 
> INFO [c.c.h.v.m.HostMO] (DirectAgent-17:ctx-38b22e90
VM i-2-168-VM not found in host cache 
> INFO [c.c.h.v.r.VmwareResource] (DirectAgent-331:ctx-894aa11d) Scan hung worker VM to
> INFO [c.c.h.v.r.VmwareResource] (DirectAgent-17:ctx-f20cffed) Scan hung worker VM to
> {noformat}
> +Root Cause Analysis+
> In case of VMware, for disk re-size we use the VM associated with the disk to perform
the re-size operation. For a detached volume since there is no associated VM the re-size failed
with 'VM does not exist' error.
> +Steps to reproduce+
> # Setup a VMware DC
> # Create a VM with a Datadisk - choose Disk offering 'Small' for the Datadisk
> # Detach the Datadisk
> # Attempt to resize the Datadisk - choose New Offering 'Medium Disk, 20 GB'
> The above will fail with a UI message 'Failed to resize volume'.

This message was sent by Atlassian JIRA

View raw message