Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
4.10.0.0
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
-
N/A
Description
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?
Attachments
Issue Links
- links to