Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 3 Jul 2017 05:59:00 +0000 (UTC)
From: "Nitesh Sarda (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13084115.1499055506000.157014.1499061540050@Atlassian.JIRA>
In-Reply-To: <JIRA.13084115.1499055506000@Atlassian.JIRA>
References: <JIRA.13084115.1499055506000@Atlassian.JIRA> <JIRA.13084115.1499055506993@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9981) Regression occurs after
 upgrading to 4.10 while registering a template.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 03 Jul 2017 05:59:08 -0000


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

Nitesh Sarda commented on CLOUDSTACK-9981:
------------------------------------------

Raise a PR for this issue. Following are the details :

https://github.com/apache/cloudstack/pull/2165

> Regression occurs after upgrading to 4.10 while registering a template.
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9981
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-998=
1
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>            Reporter: Nitesh Sarda
>
> When an environment is upgraded to 4.10, then while registering template =
for a zone from cloudstack UI will fail if it is created in older version(b=
efore 3.x).=20
> This bug got introduced with the PR#1894 for CLOUDSTACK-9700. In this PR =
a new parameter =E2=80=98zoneIds=E2=80=99 was added to the registerTemplate=
 api and is marked with the =E2=80=98since=E2=80=99 attribute as =E2=80=984=
.10.0.0=E2=80=99. since attribute is suppose to provide version for the con=
taining data, not about when parameter was introduced. Although the paramet=
er was introduced in 4.10, but it can contain the information from earlier =
version, thus it is wrongly marked here as =E2=80=984.10.0.0=E2=80=99. =20
> This issue occurs because zones from older version have UUID parameter va=
lue as Integer, whereas higher version zones have fixed format. So while fe=
tching the ZoneIds for installing templates, parsing for UUID with integer =
value fails and hence template is not installed.
> Fix :
> For the sake of backward compatibility, along with UUID, integer is also =
being parsed while retrieving ZoneId for the installing templates. Integer =
value of UUID cannot be converted into the fixed format because this value =
is used as a hard coded value in few automation scripts which runs locally =
for some customers. Hence, "since" attribute should be removed from a param=
eter command for ZoneIds.  =20


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)