[
https://issues.apache.org/jira/browse/CLOUDSTACK-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940905#comment-15940905
]
ASF GitHub Bot commented on CLOUDSTACK-9827:
--------------------------------------------
Github user nvazquez commented on the issue:
https://github.com/apache/cloudstack/pull/1994
@karuturi Travis is now failing as it doesn't find key "nfs2"
````
2017-03-24 17:33:45,621 - CRITICAL - EXCEPTION:
test_03_migration_options_storage_tags: ['Traceback (most recent call
last):\n', ' File "/opt/python/2.7.12/lib/python2.7/unittest/case.py", line
329, in run\n testMethod()\n', ' File
"/home/travis/.local/lib/python2.7/site-packages/marvin/lib/decoratorGenerators.py",
line 30, in test_wrapper\n return test(self, *args, **kwargs)\n', ' File
"/home/travis/build/apache/cloudstack/test/integration/smoke/test_primary_storage.py",
line 520, in test_03_migration_options_storage_tags\n
self.services["nfs2"],\n', "KeyError: 'nfs2'\n"]
````
It is introduced in PR #1961, can these two PRs be merged together?
> 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)
