cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9827) Storage tags stored in multiple places
Date Sat, 11 Mar 2017 04:52:04 GMT

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

ASF GitHub Bot commented on CLOUDSTACK-9827:
--------------------------------------------

Github user mike-tutkowski commented on the issue:

    https://github.com/apache/cloudstack/pull/1994
  
    I have run the following use cases successfully:
    
    PS = Primary Storage
    ST = Storage Tag
    CO = Compute Offering
    DO = Disk Offering
    V = Volume
    
    Create PS_1 with ST NFS-A
    
    Create CO_1 with ST NFS-A
    Create CO_2 with ST NFS-B
    
    Create VM_1 with CO_1 (VM starts)
    Create VM_2 with CO_2 (VM fails to find storage)
    
    Edit ST of PS_1 from NFS-A to NFS-B
    
    Create VM_2 with CO_1 (VM fails to find storage)
    Create VM_2 with CO_2 (VM starts)
    
    Create DO_1 with ST NFS-A
    Create DO_2 with ST NFS-B
    
    Create V_1 with DO_1 and attach to VM_1 (fails to find storage)
    Create V_2 with DO_2 and attach to VM_1
    
    Edit ST of PS_1 from NFS-B to NFS-A
    
    Create V_1 with DO_1 and attach to VM_1
    
    Create PS_2 with no ST
    
    Edit ST of PS_2 to NFS-B
    
    Create V_3 with DO_1 and attach to VM_2 (lands on expected PS)
    Create V_4 with DO_2 and attach to VM_2 (lands on expected PS)
    
    Create PS_3 with ST NFS-B
    
    Migrate V_4 from PS_2 to PS_3 (PS_1 is not an option)
    Migrate V_4 from PS_3 to PS_2 (PS_1 is not an option)
    
    Migrate V_3 from PS_1 to PS_2 (Neither PS_2 nor PS_3 is an option)
    
    Migrate root V of VM_1 from PS_1 to PS_2 (Neither PS_2 nor PS_3 is an option)
    
    Migrate root V of VM_2 from PS_1 to PS_3 (PS_2 and PS_3 are options)
    
    listStorageTags API returned expected results (I ran this at several points along the
way)


> Storage tags stored in multiple places
> --------------------------------------
>
>                 Key: CLOUDSTACK-9827
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9827
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.10.0.0
>         Environment: N/A
>            Reporter: Mike Tutkowski
>            Assignee: Nicolas Vazquez
>            Priority: Blocker
>             Fix For: 4.10.0.0
>
>
> I marked this as a Blocker because it concerns me that we are not handling storage tags
correctly in 4.10 and, as such, VM storage might get placed in locations that users don't
want.
> From e-mails I sent to dev@ (most recent to oldest):
> If I add a new primary storage and give it a storage tag, the tag ends up in storage_pool_details.
> If I edit an existing storage pool’s storage tags, it places them in storage_pool_tags.
> **********
> I believe I have found another bug (one that we should either fix or examine in detail
before releasing 4.10).
> It looks like we have a new table: cloud.storage_pool_tags.
> The addition of this table seems to have broken the listStorageTags API command. When
this command runs, it doesn’t pick up any storage tags for me (and I know I have one storage
tag).
> This data used to be stored in the cloud.storage_pool_details table. It’s good to put
it in its own table, but will our upgrade process move the existing tags from storage_pool_details
to storage_pool_tags?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message