Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 78D0220049E for ; Thu, 10 Aug 2017 13:09:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 773A616B1D2; Thu, 10 Aug 2017 11:09:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BDA8416B1D0 for ; Thu, 10 Aug 2017 13:09:03 +0200 (CEST) Received: (qmail 89390 invoked by uid 500); 10 Aug 2017 11:09:03 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 89375 invoked by uid 99); 10 Aug 2017 11:09:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2017 11:09:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 836C11805C0 for ; Thu, 10 Aug 2017 11:09:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id dTJ9Kl6H7U9X for ; Thu, 10 Aug 2017 11:09:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 273125F245 for ; Thu, 10 Aug 2017 11:09:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6C538E059C for ; Thu, 10 Aug 2017 11:09:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2576F2415E for ; Thu, 10 Aug 2017 11:09:00 +0000 (UTC) Date: Thu, 10 Aug 2017 11:09:00 +0000 (UTC) From: "Andrii Tkach (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-21700) Expose Patch Reversion in the Web Client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 10 Aug 2017 11:09:04 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21700: ---------------------------------- Attachment: AMBARI-21700.patch > 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)