cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkata Siva Vijayendra Bhamidipati (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-3509) Put in missing code to kick off non root volume resize operations in vmware deployments
Date Fri, 12 Jul 2013 20:57:49 GMT
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-3509:

             Summary: Put in missing code to kick off non root volume resize operations in
vmware deployments
                 Key: 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 Cloudstack currently only supports volumes
marked as KVM or XenServer hypervisor for resize
        at org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd.execute(
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask$Sync.innerRun(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

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.

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:

View raw message