cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
Date Fri, 09 Aug 2013 06:46:50 GMT

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

ASF subversion and git services commented on CLOUDSTACK-2670:
-------------------------------------------------------------

Commit 653e2e54a237ef0b26c6685185e41e92b107354a in branch refs/heads/4.2 from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=653e2e5 ]

CLOUDSTACK-2670. Migrate volume doesn't allow migration of volumes of a stopped vm.
The findStoragePoolsForMigration and migrateVolume api were explicitly blocking moving
a volume if the instance to which it was attached was stopped. Updated the check for
the same.

                
> [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages
within the cluster
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2670
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.2.0
>         Environment: Latest build from object store branch: CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>            Reporter: Sanjeev N
>            Assignee: Devdeep Singh
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
> ================
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary storage in
the cluster
> Result:
> ======
> migrate volume called findStoragePoolsFroMigration but the API returned blank response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.

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

Mime
View raw message