ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14330) In some stack service scripts "commandParams/version" is misused
Date Thu, 10 Dec 2015 21:21:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051668#comment-15051668
] 

Alejandro Fernandez commented on AMBARI-14330:
----------------------------------------------

* params.version is available during a restart command, and always during RU/EU. It may not
be there during an Install command. Its value is something like 2.3.2.0-2950, and during it
is the version upgrading/downgrading to.
* params.stack_version is of the form 2.2 or 2.3. During normal operations, it is always known.
During an RU from say HDP 2.2 to 2.3, it will always be 2.3 (even during the downgrade!!!).
During an EU, it will be 2.3 during the upgrade, and then 2.2 during the downgrade.

We need to consider all of these paths
Fresh Install (both the UI and Blueprints):
HDP 2.2
HDP 2.3.0
HDP 2.3.3.2 or higher

Upgrades:
2.2 to 2.3.0.0 and downgrade
2.2 to 2.3.2.0 and downgrade
2.3.0.0 to 2.3.2.0 and downgrade
2.3.2.0 to 2.3.4.0 and downgrade

> In some stack service scripts "commandParams/version" is misused
> ----------------------------------------------------------------
>
>                 Key: AMBARI-14330
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14330
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>             Fix For: 2.3.0
>
>         Attachments: AMBARI-14330.patch
>
>
> https://issues.apache.org/jira/browse/AMBARI-14270 -> in this change, the issue was
fixed, but with redefining "commandParams/version" , this parameter should be used only on
upgrade



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message