[jira] [Commented] (AMBARI-22220) Should be able to switch the extension version to which a stack version is linked

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-22220:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12891768/AMBARI-22220.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 5 new or modified test files.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:red}-1 core tests{color}.  The test build failed in [ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12506//artifact/patch-work/testrun_ambari-server.txt] 

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12506//console

This message is automatically generated.

> Should be able to switch the extension version to which a stack version is linked 
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-22220
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22220
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: trunk, 2.5.0, 2.6.0
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>             Fix For: trunk
>
>         Attachments: AMBARI-22220.patch
>
>
> Currently the only way to switch the extension version to which a stack version is linked is to perform the following actions:
> * Stop the extension services
> * Reregister (delete) the extension services
> * Unlink the old extension version
> * Link the new extension version
> * Add the extension services back
> The REST API should allow us to do an update action on the extension link.  In this manner, if we were running an upgrade from HDP 2.6.1 to 2.6.3 (or something similar) which both use the HDP 2.6 stack version then we could perform the extension link switch as a manual step during the upgrade process.



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