cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9827) Storage tags stored in multiple places
Date Fri, 24 Mar 2017 17:03:41 GMT


ASF GitHub Bot commented on CLOUDSTACK-9827:

Github user nvazquez commented on the issue:
    @karuturi I refactored last marvin test which was failing on Travis. These are results
in our env:
    [root@ussarlabcsmgt41 cloudstack]# cat /tmp//MarvinLogs//4GSNSY/results.txt
    Test primary storage pools - XEN. Not Supported for kvm,hyperv,vmware ... SKIP: iscsi
primary storage not supported on kvm, VMWare, Hyper-V, or LXC
    Test primary storage pools - XEN, KVM, VMWare. Not Supported for hyperv ... === TestName:
test_01_primary_storage_nfs | Status : SUCCESS ===
    Test Deploy VMS using different Service Offerings with Storage Tags ... === TestName:
test_01_deploy_vms_storage_tags | Status : SUCCESS ===
    Test Edit Storage Tags ... === TestName: test_02_edit_primary_storage_tags | Status :
    Test Volume migration options for Storage Pools with different Storage Tags ... === TestName:
test_03_migration_options_storage_tags | Status : SUCCESS ===
    Ran 5 tests in 442.216s
    OK (SKIP=1)
    @rhtyd @borisstoyanov @jburwell on `` we are creating 2 primary
storages, using urls in `"nfs"` and `"nfs2"` test data templates. As PR #1961 uses `"nfs2"`
template on ``, should it be a problem for BlueOrangutan?

> Storage tags stored in multiple places
> --------------------------------------
>                 Key: CLOUDSTACK-9827
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions:
>         Environment: N/A
>            Reporter: Mike Tutkowski
>            Assignee: Nicolas Vazquez
>            Priority: Blocker
>             Fix For:
> 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
> 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
> 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

View raw message