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 0A6FA200D0B for ; Mon, 28 Aug 2017 13:04:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 08ACF1644CA; Mon, 28 Aug 2017 11:04:09 +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 57CD61644D3 for ; Mon, 28 Aug 2017 13:04:08 +0200 (CEST) Received: (qmail 94882 invoked by uid 500); 28 Aug 2017 11:04:07 -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 94872 invoked by uid 99); 28 Aug 2017 11:04:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2017 11:04:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 729E7C2339 for ; Mon, 28 Aug 2017 11:04:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id zKQu-llH9mRf for ; Mon, 28 Aug 2017 11:04:04 +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 80FF45FC43 for ; Mon, 28 Aug 2017 11:04:03 +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 6E43BE0EA7 for ; Mon, 28 Aug 2017 11:04:01 +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 8022F2538E for ; Mon, 28 Aug 2017 11:04:00 +0000 (UTC) Date: Mon, 28 Aug 2017 11:04:00 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 28 Aug 2017 11:04:09 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143647#comment-16143647 ] Hudson commented on AMBARI-21709: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7947 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7947/]) AMBARI-21709 Finalize Warns that it is Permanent Even For PATCH (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2a57959f5b8ddaa545dba1b5496f82902fa0e75c]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js > Finalize Warns that it is Permanent Even For PATCH Upgrades > ----------------------------------------------------------- > > Key: AMBARI-21709 > URL: https://issues.apache.org/jira/browse/AMBARI-21709 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.5.3 > Reporter: Andrii Tkach > Assignee: Andrii Tkach > Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21709.patch, Screen Shot 2017-08-03 at 2.01.52 PM.png > > > Perform either a {{PATCH}} or {{MAINT}} upgrade and get to Finalize. The upgrade wizard warns that finalization is permanent. > {quote} > Your cluster version has been upgraded. Click on Finalize when you are ready to finalize the upgrade and commit to the new version. You are strongly encouraged to run tests on your cluster to ensure it is fully operational before finalizing. You cannot go back to the original version once the upgrade is finalized. > {quote} > This is not true for certain upgrade types. Finalization is a required step, yes, but you can still revert {{PATCH}} and {{MAINT}} upgrades that have finalized. The message for these types should read something like: > {quote} > The {{PATCH}} upgrade to HDP-2.5.4.0-1234 is ready to be completed. After finalization, the patch can be reverted from the Stacks and Versions page if it is no longer required." > {quote} -- This message was sent by Atlassian JIRA (v6.4.14#64029)