[ https://issues.apache.org/jira/browse/CLOUDSTACK-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devdeep Singh resolved CLOUDSTACK-6809. --------------------------------------- Resolution: Not a Problem We do not allow live storage motion of a volume from cluster wide to zone wide primary storage. That is why the findStoragePoolsForMigration api lists only zone wide pools for a volume on zone wide storage and cluster wide pools for a volume on cluster wide storage. This is the expected behavior. > listStoragePoolsForMigration doesn't list the zone wide primary storages if > the volume is on cluster-wide storage, and doesn't list cwps if volume is on > zwps > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-6809 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6809 > 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.4.0 > Environment: HyperV Advanced zone setup with cluster wide, zone wide > and local storages. > Reporter: Abhinav Roy > Assignee: Devdeep Singh > Priority: Critical > Labels: S1 > Fix For: 4.4.0 > > > Steps : > ====================== > 1. Deploy a advanced zone hyperv setup with 2 clusters. > 2. Have 2 primary storages in each of the clusters and 2 zone wide primary > storages. > 3. Deploy a VM v1 on cluster wide primary storage in cluster1/2 > 4. Deply a VM v2 on zone wide primary storage in cluster1/2. > 5. Now do a listStoragePoolsForMigration for ROOT volumes of v1 and v2 > Expected behavior : > ===================== > All zone wide primary storage and cluster wide primary storages available > should be listed > Observed behavior : > ===================== > 1. list for v1 doesn't show any zone wide primary storage. > monkey# find storagepoolsformigration id=31 > count = 1 > storagepool: > name = p2 > id = b3fcb49c-b870-33e6-86f2-bb1eb72cceef > clusterid = 5e649bb3-b2a8-49f9-9db0-ab50546d306a > clustername = cluster1 > created = 2014-05-26T11:27:01+0530 > disksizeallocated = 1073741824 > disksizetotal = 998772830208 > disksizeused = 157359783936 > ipaddress = SMB19 > jobstatus = 0 > overprovisionfactor = 2.0 > path = /hyperv-share/abhinav-ps2?user=abhinavroy&domain=BLR > podid = f36ada26-ecf2-4869-ba4f-d844ec23531a > podname = hyperv > scope = CLUSTER > state = Up > suitableformigration = False > type = SMB > zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 > zonename = hyperv > 2. list for v2 doesn't show any cluster wide primary storage > monkey# find storagepoolsformigration id=30 > count = 1 > storagepool: > name = zwps > id = 3f754d4f-365c-3bd1-93d1-c3c9947fb3cc > created = 2014-05-30T11:57:02+0530 > disksizeallocated = 0 > disksizetotal = 998772830208 > hypervisor = Hyperv > ipaddress = SMB19 > jobstatus = 0 > overprovisionfactor = 2.0 > path = /hyperv-share/abhinav-ps6?user=abhinavroy&domain=BLR > scope = ZONE > state = Up > suitableformigration = False > type = SMB > zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 > zonename = hyperv > NOTE : Even though the pools are not listed, if the migration is attempted > using the API and passing these storage pool ids, migration succeeds from > zwps to cwps and vice-versa -- This message was sent by Atlassian JIRA (v6.2#6252)