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 DCF47200D0A for ; Wed, 4 Oct 2017 20:24:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DB3E51609DD; Wed, 4 Oct 2017 18:24: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 2D5091609D6 for ; Wed, 4 Oct 2017 20:24:09 +0200 (CEST) Received: (qmail 47093 invoked by uid 500); 4 Oct 2017 18:24: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 46971 invoked by uid 99); 4 Oct 2017 18:24:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Oct 2017 18:24:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 92C0DC61DB for ; Wed, 4 Oct 2017 18:24:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id HsxW2qXX4foh for ; Wed, 4 Oct 2017 18:24: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 501965FE43 for ; Wed, 4 Oct 2017 18:24: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 9D8FCE0D6A for ; Wed, 4 Oct 2017 18:24: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 5A624242F3 for ; Wed, 4 Oct 2017 18:24:00 +0000 (UTC) Date: Wed, 4 Oct 2017 18:24:00 +0000 (UTC) From: "Aleksandr Kovalenko (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-22134) UI Fixes for Maint Repo Version Display MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 04 Oct 2017 18:24:10 -0000 [ https://issues.apache.org/jira/browse/AMBARI-22134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191775#comment-16191775 ] Aleksandr Kovalenko commented on AMBARI-22134: ---------------------------------------------- +1 for the patch > UI Fixes for Maint Repo Version Display > --------------------------------------- > > Key: AMBARI-22134 > URL: https://issues.apache.org/jira/browse/AMBARI-22134 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.6.0 > Reporter: Antonenko Alexander > Assignee: Antonenko Alexander > Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22134.patch > > > STR: > Install 2.6.0.0 base of ZK + STORM. > Register/Install/Upgrade a MAINT VDF to 2.6.0.3 that includes STORM + KAFKA > Upgrade will be Storm only > Register/Install/Upgrade another MAINT VDF to 2.6.3.0 that includes STORM+KAFKA > Add Kafka service. > The 2nd repo becomes OUT_OF_SYNC (that's ok) > Reinstall and Upgrade (Kafka becomes upgraded) > When reverting the (correct) last upgrade, orchestration would be ONLY for Kafka, since that was the last upgrade, but the dialog says that both Storm and Kafka will be reverted. This is incorrect, it should only show Kafka. This information is correct in the Upgrade History tab. You should be querying the upgrade endpoint for revert_upgrade_id to know what to show on the popup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)