You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2017/12/16 08:54:00 UTC
[jira] [Resolved] (CLOUDSTACK-9953) [Vmware][UI] The root disk
resize option for VMWare should only be set when required global setting
allows it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohit Yadav resolved CLOUDSTACK-9953.
-------------------------------------
Resolution: Fixed
Assignee: Rohit Yadav
Fix Version/s: 4.11.0.0
Root disk during VM start will only be resized when disk chain is one, or when scsi bus was setup. For ide, it will skip resize operation and this error won't cause VMs to fail starting (or the general exception of insufficient capacity thrown).
> [Vmware][UI] The root disk resize option for VMWare should only be set when required global setting allows it
> -------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9953
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9953
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI, VMware
> Affects Versions: 4.10.1.0
> Environment: vmware 5.5, MS 4.10
> Reporter: Abhinandan Prateek
> Assignee: Rohit Yadav
> Priority: Minor
> Fix For: Future, 4.11.0.0
>
>
> When I give a size of 10GB to the root disk while creating VM I see and insufficient capacity exception in the UI.
> In the logs I see that the MS failed to resize disk:
> 200, unit number: 1
> 2017-06-10 01:51:43,691 INFO [c.c.h.v.m.VirtualMachineMO] (DirectAgent-448:ctx-8f797ec5 10.2.2.39, job-78/job-80, cmd: StartCommand) (logid:1725a568) Test against disk backing : [0ef53da61ee53329a665b93d3b000ce1] i-2-9-VM/ROOT-9.vmdk
> 2017-06-10 01:51:43,691 INFO [c.c.h.v.m.VirtualMachineMO] (DirectAgent-448:ctx-8f797ec5 10.2.2.39, job-78/job-80, cmd: StartCommand) (logid:1725a568) Disk backing : [0ef53da61ee53329a665b93d3b000ce1] i-2-9-VM/ROOT-9.vmdk matches ==> ide0:1
> 2017-06-10 01:51:43,713 INFO [c.c.h.v.r.VmwareResource] (DirectAgent-448:ctx-8f797ec5 10.2.2.39, job-78/job-80, cmd: StartCommand) (logid:1725a568) Found existing disk info from volume path: ROOT-9
> 2017-06-10 01:51:43,713 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-448:ctx-8f797ec5 10.2.2.39, job-78/job-80, cmd: StartCommand) (logid:1725a568) Unsupported Disk chain length 2
> 2017-06-10 01:51:43,713 INFO [c.c.h.v.u.VmwareHelper] (DirectAgent-448:ctx-8f797ec5 10.2.2.39, job-78/job-80, cmd: StartCommand) (logid:1725a568) [ignored]failed toi get message for exception: Unsupported Disk chain length 2
> 2017-06-10 01:51:43,718 WARN [c.c.h.v.r.VmwareResource] (DirectAgent-448:ctx-8f797ec5 10.2.2.39, job-78/job-80, cmd: StartCommand) (logid:1725a568) StartCommand failed due to Exception: java.lang.Exception
> Message: Unsupported Disk chain length 2
> java.lang.Exception: Unsupported Disk chain length 2
> at com.cloud.hypervisor.vmware.resource.VmwareResource.resizeRootDisk(VmwareResource.java:2122)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2044)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:470)
> at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
> 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)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)