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 B10D4200D19 for ; Fri, 6 Oct 2017 10:29:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AFA59160BDB; Fri, 6 Oct 2017 08:29:06 +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 0489E1609D0 for ; Fri, 6 Oct 2017 10:29:05 +0200 (CEST) Received: (qmail 85467 invoked by uid 500); 6 Oct 2017 08:29:04 -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 85455 invoked by uid 99); 6 Oct 2017 08:29:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Oct 2017 08:29:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 711B71A1659 for ; Fri, 6 Oct 2017 08:29:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -98.002 X-Spam-Level: X-Spam-Status: No, score=-98.002 tagged_above=-999 required=6.31 tests=[KAM_BADIPHTTP=2, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id J9E8gDkyxGFG for ; Fri, 6 Oct 2017 08:29:03 +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 B42ED5FC3C for ; Fri, 6 Oct 2017 08:29: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 3FED4E0A3A for ; Fri, 6 Oct 2017 08:29:03 +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 7B8632415E for ; Fri, 6 Oct 2017 08:29:01 +0000 (UTC) Date: Fri, 6 Oct 2017 08:29:00 +0000 (UTC) From: "Supreeth Sharma (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-22154) Install and upgrade options are shown for current and already upgraded stack versions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 06 Oct 2017 08:29:06 -0000 Supreeth Sharma created AMBARI-22154: ---------------------------------------- Summary: Install and upgrade options are shown for current and already upgraded stack versions Key: AMBARI-22154 URL: https://issues.apache.org/jira/browse/AMBARI-22154 Project: Ambari Issue Type: Bug Components: ambari-upgrade Affects Versions: 2.6.0 Environment: ambari-server --version 2.6.0.0-185 Reporter: Supreeth Sharma Priority: Critical Fix For: 2.6.0 This scenario looks intermittent. Live cluster where issue occured: http://172.27.69.192:8080/#/main/admin/stack/versions Issue 1 : After performing downgrade, it started to show 'out of sync' for all previously upgraded stack including base stack. Attaching the screenshot. Issue 2 : Its allowing to install previously installed stack including base. Test steps performed : 1) Performed ambari upgrade from 2.5.2.0 to 2.6.0.0-185 2) Performed the patch upgrade in batch of 3. 3) Performed the downgrade before finalizing the 3rd upgrade. 4) After performing downgrade, UI is showing out of sync for previously installed stacks and allowing them to reinstall. -- This message was sent by Atlassian JIRA (v6.4.14#64029)