[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Likitha Shetty resolved CLOUDSTACK-5786.
----------------------------------------

    Resolution: Not A Problem

This is the expected behavior for Storage Migration.

CS allows Storage Migration to a destination pool whose tags don't match that 
of the disk that is being migrated. It is up to the Admin to decide which pool 
to migrate to. Refer - [https://issues.apache.org/jira/browse/CLOUDSTACK-2734]

As far as listing out suitable pools for migration is concerned,
In case of live migration findStoragePoolsForMigration API will list out pools 
whose tags don't match the disk that is being migrated as *unsuitable*.
And In case of migration of detached volume since we list all storage pools (as 
mentioned in [https://issues.apache.org/jira/browse/CLOUDSTACK-5783]) it 
doesn't matter what tags are present.



> [vmware] Vcenter 5.5  host ESXi 5.5 If the tags on the destination storage 
> pool do not match the disk offering with which a volume is created; migration 
> is allowed.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5786
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5786
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: MS    build  1/2/2014
> vcenter 5.5     host 1    host 2     ESXi 5.5
>            Reporter: angeline shen
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.3.0
>
>         Attachments: management-server(3).log.gz, 
> management-server(3).log.gz, vm10.png
>
>
> 1. SO   512tag1   storage tag:  tag1
> 4 primary storage:   PC1:  tag3    PC2:  tag3    PZ3:   tag1      PZ4:
> 2.deploy VM 512tag1 with disk.   ROOT vol  on PZ3    DATA vol on PC1
> 3. VM stop.    ROOT vol > volume migrate shows PZ4 (unsuitable)
> Migration FAIL
> 4. DATA vol > volume migrate shows 6 primary storage > PZ3
> Migration FAIL



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to