Srikanteswararao Talluri created CLOUDSTACK-3912:
----------------------------------------------------
Summary: resize volume is failing
Key: CLOUDSTACK-3912
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3912
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: xenserver
Reporter: Srikanteswararao Talluri
Priority: Blocker
Fix For: 4.2.0
Steps to reproduce:
===============
1. resize a data volume after stopping the VM to which it is attached to.
===START=== 10.101.255.7 -- GET
command=resizeVolume&id=e67740b4-b5fe-457a-ad23-f6b0e9e27eaa&shrinkok=false&diskofferingid=ad0e677e-6d01-4a8d-8f74-ee3721702b89&response=json&sessionkey=KcomtGj8N555RYPKEkmivNZN6wA%3D&_=1375115000024
2013-07-30 03:16:19,637 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-23:null) submit async job-172 = [
a62083ea-7ce2-4e41-bc98-b8772282e44e ], details: AsyncJobVO {id:172, userId: 2,
accountId: 2, sessionKey: null, instanceType: Volume, instanceId: null, cmd:
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd, cmdOriginator:
null, cmdInfo:
{"response":"json","id":"e67740b4-b5fe-457a-ad23-f6b0e9e27eaa","sessionkey":"KcomtGj8N555RYPKEkmivNZN6wA\u003d","shrinkok":"false","cmdEventType":"VOLUME.RESIZE","ctxUserId":"2","httpmethod":"GET","_":"1375115000024","ctxAccountId":"2","diskofferingid":"ad0e677e-6d01-4a8d-8f74-ee3721702b89","ctxStartEventId":"748"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-30 03:16:19,643 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===END=== 10.101.255.7 -- GET
command=resizeVolume&id=e67740b4-b5fe-457a-ad23-f6b0e9e27eaa&shrinkok=false&diskofferingid=ad0e677e-6d01-4a8d-8f74-ee3721702b89&response=json&sessionkey=KcomtGj8N555RYPKEkmivNZN6wA%3D&_=1375115000024
2013-07-30 03:16:19,646 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-39:job-172 = [ a62083ea-7ce2-4e41-bc98-b8772282e44e ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-172 = [
a62083ea-7ce2-4e41-bc98-b8772282e44e ]
2013-07-30 03:16:19,768 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-39:job-172 = [ a62083ea-7ce2-4e41-bc98-b8772282e44e ]) Unexpected
exception while executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd
com.cloud.exception.InvalidParameterValueException: Can't resize a volume that
has never been attached, not sure which hypervisor type. Recreate volume to
resize.
at
com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1109)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:186)
at
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(ResizeVolumeCmd.java:137)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-07-30 03:16:19,810 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-39:job-172 = [ a62083ea-7ce2-4e41-bc98-b8772282e44e ]) Complete
async job-172 = [ a62083ea-7ce2-4e41-bc98-b8772282e44e ], jobStatus: 2,
resultCode: 530, result: Error Code: 530 Error text: Can't resize a volume that
has never been attached, not sure which hypervisor type. Recreate volume to
resize.
Logs can be found:
--
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
