[jira] [Commented] (AMBARI-21923) Web Client Should Only Show Revert Action On Revertable Repositories

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

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

Hadoop QA commented on AMBARI-21923:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12886379/AMBARI-21923_trunk.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 4 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-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12169//artifact/patch-work/testrun_ambari-web.txt] 

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

This message is automatically generated.

> Web Client Should Only Show Revert Action On Revertable Repositories
> --------------------------------------------------------------------
>
>                 Key: AMBARI-21923
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21923
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.6.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21923_branch26.patch, AMBARI-21923_trunk.patch
>
>
> Register, install, and apply several different PATCH repositories and the web client allows each of them to be reverted in any order. The backend needs to provide a way to indicate that only the most recent applied patch can be reverted.
> The backed should return a value, such as ClusterStackVersions/supports_revert which clients, such as the web client, can use. 
> The backend will also now return ClusterStackVersions/revert_upgrade_id in the event that the upgrade is revertable. This will fix a bug where the web client was choosing the wrong upgrade to revert. This value should be used when making the call to the upgrades endpoint Upgrade/revert_upgrade_id when initiating an upgrade reversion.



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