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

Hadoop QA commented on AMBARI-21700:
------------------------------------

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

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> Expose Patch Reversion in the Web Client
> ----------------------------------------
>
>                 Key: AMBARI-21700
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21700
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.5.3
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Blocker
>             Fix For: 2.5.3
>
>         Attachments: AMBARI-21700.patch, patch-revert.gif
>
>
> The web client will need to expose the ability to revert a patch which was 
> successfully applied to one or more services. Patch upgrades allows one or 
> more services to effectively be "patched" to a new version. Some facts:
> - Patching will only apply to the current stack. If the cluster was installed 
> with HDP 2.5, then all patches must be scoped to 2.5.x.y - you cannot patch 
> outside the stack.
> - Each service/component now exposes the repository version they are on. 
> The following work should be scoped in this Jira. If the scope turns out to 
> be too great, then it can be broken up into several JIras:
> - The stacks and versions page will change to show multiple "CURRENT" stacks.
> - The most recent patch will be able to be reverted. The revert button will 
> only show for the newest applied patch. Once reverted, the prior patch can be 
> reverted now.
> - If a full stack upgrade is performed, then the bar is reset, regardless the 
> version upgraded to.



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

Reply via email to