You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/07/23 20:28:48 UTC
[jira] [Assigned] (CLOUDSTACK-3736) findStoragePoolsForMigration
API returns empty response if the VM is in stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alena Prokharchyk reassigned CLOUDSTACK-3736:
---------------------------------------------
Assignee: Alena Prokharchyk
> findStoragePoolsForMigration API returns empty response if the VM is in stopped state
> -------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3736
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3736
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Storage Controller
> Affects Versions: 4.2.0
> Environment: Latest build from ACS 4.2 branch
> Storage: Used NFS for both primary and secondary
> Reporter: Sanjeev N
> Assignee: Alena Prokharchyk
> Priority: Critical
> Fix For: 4.2.0
>
>
> findStoragePoolsForMigration API returns empty response if the VM is in stopped state
> Steps to Reproduce:
> ================
> 1.Bring up CS with xen cluster
> 2.Add primary storage ps1 to cluster
> 3.Deploy guest vm usign default cent os template with both root and data disk
> 4.Add another primary storage ps2 in the same cluster
> 5.When the vm is in running state try to migrate the data disk to primary storage ps2.
> storage migration executes findStoragePoolsForMigration API with data disk id and will return ps2 as the available storage pool for volume migration which is expected
> 6.Stop the guest vm and repeat step5.
> Observations:
> ===========
> findStoragePoolsForMigration API returns empty response even though ps2 is available for storage migration.
> Following API was executed when migrate volume button on the disk was clicked from the UI:
> http://10.147.59.126:8080/client/api?command=findStoragePoolsForMigration&id=0d627eec-3824-4d35-8997-853472502454&response=json&sessionkey=mGrsWfEH9yd0ZXdope6MQSGMhxQ%3D&_=1374585064040
> Following is the volume state in the cloud db:
> mysql> select * from volumes where uuid='0d627eec-3824-4d35-8997-853472502454'\G;
> *************************** 1. row ***************************
> id: 10
> account_id: 2
> domain_id: 1
> pool_id: 1
> last_pool_id: NULL
> instance_id: 3
> device_id: 1
> name: cent62
> uuid: 0d627eec-3824-4d35-8997-853472502454
> size: 10737418240
> folder: NULL
> path: b2b96197-665a-40cd-a52b-de0506c45a8e
> pod_id: NULL
> data_center_id: 1
> iscsi_name: NULL
> host_ip: NULL
> volume_type: DATADISK
> pool_type: NULL
> disk_offering_id: 6
> template_id: NULL
> first_snapshot_backup_uuid: NULL
> recreatable: 0
> created: 2013-07-23 12:36:22
> attached: 2013-07-23 12:52:40
> updated: 2013-07-23 13:09:08
> removed: NULL
> state: Ready
> chain_info: NULL
> update_count: 6
> disk_type: NULL
> display_volume: 0
> format: VHD
> min_iops: NULL
> max_iops: NULL
> 1 row in set (0.00 sec)
> ERROR:
> No query specified
--
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