You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Venkata Siva Vijayendra Bhamidipati (JIRA)" <ji...@apache.org> on 2013/07/12 23:03:55 UTC
[jira] [Commented] (CLOUDSTACK-3509) Put in missing code to kick
off non root volume resize operations in vmware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707367#comment-13707367 ]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3509:
-----------------------------------------------------------------
Patch posted to https://reviews.apache.org/r/12521/
> Put in missing code to kick off non root volume resize operations in vmware deployments
> ---------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3509
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3509
> 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: vmware deployments in cloudstack 4.2.
> Reporter: Venkata Siva Vijayendra Bhamidipati
> Assignee: Venkata Siva Vijayendra Bhamidipati
>
> Currently, on master, issuing a volume resize operation on a non-root volume of a guest VM resident on ESX hypervisor throws the following exception:
> ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-3:job-23 = [ 8f455c05-6b91-4eb0-aa95-a80993263769 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd
> com.cloud.exception.InvalidParameterValueException: Cloudstack currently only supports volumes marked as KVM or XenServer hypervisor for resize
> at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:1127)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:189)
> 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:532)
> 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:1146)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> The volume resize code for XS, KVM and VMWare was checked in by Marcus on behalf of Hongtu, but a small part of that code was inadvertently overwritten in a later commit, resulting in the above loss of functionality. Creating this bug to track the re-checkin of that missing hypervisor check in VolumeManagerImpl. The original ticket tracking the volume resize feature is CLOUDSTACK-644 (https://issues.apache.org/jira/browse/CLOUDSTACK-644).
--
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