Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 9 Mar 2017 20:59:38 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13049101.1488934246000.26651.1489093178014@Atlassian.JIRA>
In-Reply-To: <JIRA.13049101.1488934246000@Atlassian.JIRA>
References: <JIRA.13049101.1488934246000@Atlassian.JIRA> <JIRA.13049101.1488934246891@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9827) Storage tags stored in
 multiple places
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 09 Mar 2017 20:59:43 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9827?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15903853#comment-15903853 ]=20

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

Github user rafaelweingartner commented on the issue:

    https://github.com/apache/cloudstack/pull/1994
 =20
    @nvazquez I am assuming the change needed to fix the bug is line 135 at=
 PrimaryDataStoreHelper.java?
    The other changes are regarding code conformity


> Storage tags stored in multiple places
> --------------------------------------
>
>                 Key: CLOUDSTACK-9827
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-982=
7
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          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 handlin=
g 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=E2=80=99s storage tags, it places them=
 in storage_pool_tags.
> **********
> I believe I have found another bug (one that we should either fix or exam=
ine 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 c=
ommand. When this command runs, it doesn=E2=80=99t 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=
=E2=80=99s good to put it in its own table, but will our upgrade process mo=
ve the existing tags from storage_pool_details to storage_pool_tags?


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