Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 27 Jul 2013 14:35:48 +0000 (UTC)
From: "Rajesh Battala (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12660198.1374934803887.123746.1374935748756@arcas>
In-Reply-To: <JIRA.12660198.1374934803887@arcas>
References: <JIRA.12660198.1374934803887@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-3877) Unable to Resize Volume (kvm,
 vmware)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721636#comment-13721636 ] 

Rajesh Battala commented on CLOUDSTACK-3877:
--------------------------------------------

mentioned commit id fixes https://issues.apache.org/jira/browse/CLOUDSTACK-3856 
this issue is happening while determining the hypervisor type for a volume. 
for ZWPS, it will return the hypervisor because, in storage pool we store the hypervisor type if the pool is added of scoe ZONE. 
if the pool is of scope Cluster hypervisor type will be NULL

we support volume resize when the volume is present on ZONE scope and Cluster scope. 
they way of hypervisor type extraction from the sql query result should be change which will resolve this blocker.
Am working on it will post the patch in few mins
                
> Unable to Resize Volume (kvm, vmware)
> -------------------------------------
>
>                 Key: CLOUDSTACK-3877
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3877
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Storage Controller
>    Affects Versions: 4.1.1, 4.2.0
>         Environment: kvm, 4.2 code.
> instances running on Kvm. and volumes attached and present in cluster scope primary storage
>            Reporter: Rajesh Battala
>            Assignee: Rajesh Battala
>            Priority: Blocker
>             Fix For: 4.1.1, 4.2.0
>
>
> ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-8:job-40 = [ 89b9f53d-abaa-47fe-91ba-13795b647a2b ]) 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:1108)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at com.cloud.storage.VolumeManagerImpl.resizeVolume(VolumeManagerImpl.java:185)
>         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:722)

--
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