[
https://issues.apache.org/jira/browse/CLOUDSTACK-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan Kumar Bandarupally closed CLOUDSTACK-3392.
------------------------------------------------
Resolution: Won't Fix
> resizeDataVolume throws an expception when trying to shrink volume on
> XenServer and KVM
> ---------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3392
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3392
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
> Affects Versions: 4.2.0
> Environment: Management Server: RHEL 6.3
> Xenserver: 6.1
> Reporter: Pavan Kumar Bandarupally
> Assignee: Likitha Shetty
> Priority: Critical
> Labels: integration-test
> Fix For: 4.2.0
>
> Attachments: KVM log.rar, management-server-log.rar
>
>
> An exception is thrown when trying to re-size(shrink) a data volume for a
> guest VM hosted on Xenserver. The guest VM is shutdown before resizing as
> resize on Xenserver is supported on offline VMs
> Note: Increasing the volume works fine. The exception is thrown only for
> shrink. Attaching MS log.
> Stack Trace:
> ---------------
> 2013-07-08 20:18:36,971 WARN [xen.resource.CitrixResourceBase]
> (DirectAgent-37:null) Unable to resize volume
> SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not allowed]
> at com.xensource.xenapi.Types.checkResponse(Types.java:1936)
> at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
> at
> com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
> at com.xensource.xenapi.VDI.resize(VDI.java:1350)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:6155)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:516)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> at
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> 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$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-08 20:18:36,972 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-37:null) Seq 1-1025154837: Response Received:
> 2013-07-08 20:18:36,973 DEBUG [agent.transport.Request] (DirectAgent-37:null)
> Seq 1-1025154837: Processing: { Ans: , MgmtId: 7541090156566, via: 1, Ver:
> v1, Flags: 10,
> [{"storage.ResizeVolumeAnswer":{"newSize":0,"result":false,"details":"failed
> to resize volume:SR_BACKEND_FAILURE_79VDI Invalid size [opterr=shrinking not
> allowed]","wait":0}}] }
> 2013-07-08 20:18:36,974 DEBUG [agent.transport.Request]
> (Job-Executor-36:job-61) Seq 1-1025154837: Received: { Ans: , MgmtId:
> 7541090156566, via: 1, Ver: v1, Flags: 10, { ResizeVolumeAnswer } }
> 2013-07-08 20:18:37,029 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-36:job-61) Complete async job-61, jobStatus: 1, resultCode: 0,
> result: org.apache.cloudstack.api.response.VolumeResponse@1ff504a5
> 2013-07-08 20:18:37,044 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-36:job-61) Done executing
> org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-61
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
