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 B4B25200CB7 for ; Fri, 30 Jun 2017 15:02:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B27DC160BF6; Fri, 30 Jun 2017 13:02:03 +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 05AC0160BDD for ; Fri, 30 Jun 2017 15:02:02 +0200 (CEST) Received: (qmail 2697 invoked by uid 500); 30 Jun 2017 13:02:02 -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 2684 invoked by uid 99); 30 Jun 2017 13:02:02 -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; Fri, 30 Jun 2017 13:02:02 +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 B66B5C1865 for ; Fri, 30 Jun 2017 13:02:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.011 X-Spam-Level: X-Spam-Status: No, score=-100.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qnwOawwVaLZV for ; Fri, 30 Jun 2017 13:02:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E09BB5FDA3 for ; Fri, 30 Jun 2017 13:02:00 +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 6E8BAE069F for ; Fri, 30 Jun 2017 13:02: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 25BDA245A9 for ; Fri, 30 Jun 2017 13:02:00 +0000 (UTC) Date: Fri, 30 Jun 2017 13:02:00 +0000 (UTC) From: "Andrii Tkach (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-21381) Various Places in the Web Client Assume The Stack Name MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 30 Jun 2017 13:02:03 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21381: ---------------------------------- Description: Various places in the web client assume that the stack name is the same as the current stack of the cluster. This is incorrect when the cluster have been upgraded from a prior stack vendor. STR: - Install non-HDP stack - Upgrade to Apache Ambari 2.5.2 - Perform an upgrade to HDP 2.6 The following places are known areas where the information is incorrectly displayed: - The upgrade wizard title - the upgrade history The fact that we only display the "version" makes it seem like we didn't change stack vendors. was: Various places in the web client assume that the stack name is the same as the current stack of the cluster. This is incorrect when the cluster have been upgraded from a prior stack vendor. STR: - Install BigInsights Ambari 4.2.0 or 4.2.5 - Upgrade to Apache Ambari 2.5.2 - Perform an upgrade to HDP 2.6 The following places are known areas where the information is incorrectly displayed: - The upgrade wizard title - the upgrade history The fact that we only display the "version" makes it seem like we didn't change stack vendors. > Various Places in the Web Client Assume The Stack Name > ------------------------------------------------------ > > Key: AMBARI-21381 > URL: https://issues.apache.org/jira/browse/AMBARI-21381 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.5.2 > Reporter: Andrii Tkach > Assignee: Andrii Tkach > Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21381.patch > > > Various places in the web client assume that the stack name is the same as the current stack of the cluster. This is incorrect when the cluster have been upgraded from a prior stack vendor. > STR: > - Install non-HDP stack > - Upgrade to Apache Ambari 2.5.2 > - Perform an upgrade to HDP 2.6 > The following places are known areas where the information is incorrectly displayed: > - The upgrade wizard title > - the upgrade history > The fact that we only display the "version" makes it seem like we didn't change stack vendors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)