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 61977200C42 for ; Sat, 11 Mar 2017 01:42:14 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 601FE160B82; Sat, 11 Mar 2017 00:42:14 +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 A9704160B79 for ; Sat, 11 Mar 2017 01:42:13 +0100 (CET) Received: (qmail 95529 invoked by uid 500); 11 Mar 2017 00:42:12 -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 95520 invoked by uid 99); 11 Mar 2017 00:42:12 -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; Sat, 11 Mar 2017 00:42:12 +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 5F140C25AC for ; Sat, 11 Mar 2017 00:42:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] 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 Ps5WtETTLeLn for ; Sat, 11 Mar 2017 00:42:11 +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 A912E5F1F4 for ; Sat, 11 Mar 2017 00:42:10 +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 D14B3E0045 for ; Sat, 11 Mar 2017 00:42:09 +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 7B436243AC for ; Sat, 11 Mar 2017 00:42:04 +0000 (UTC) Date: Sat, 11 Mar 2017 00:42:04 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 11 Mar 2017 00:42:14 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905940#comment-15905940 ] Hadoop QA commented on AMBARI-20401: ------------------------------------ {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12857416/AMBARI-20401.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/10977//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10977//console This message is automatically generated. > HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group > ------------------------------------------------------------------------------------------------ > > Key: AMBARI-20401 > URL: https://issues.apache.org/jira/browse/AMBARI-20401 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.5.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20401.patch > > > # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts with only masters, 2 hosts with only slaves, 1 host with only clients) > # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only client components) > In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal' > Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any master/slave components it is already considered that components are stopped on this host and the entry shows up in wizard. > Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier Upgrades items are still Pending. > Thanks to [~shavi71] for finding this... -- This message was sent by Atlassian JIRA (v6.3.15#6346)