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 50800200CFC for ; Thu, 24 Aug 2017 05:18:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4EE3516A337; Thu, 24 Aug 2017 03:18:05 +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 9537616A320 for ; Thu, 24 Aug 2017 05:18:04 +0200 (CEST) Received: (qmail 70818 invoked by uid 500); 24 Aug 2017 03:18: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 70809 invoked by uid 99); 24 Aug 2017 03:18:03 -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; Thu, 24 Aug 2017 03:18:03 +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 43C021A06D3 for ; Thu, 24 Aug 2017 03:18:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id AgKESmP1-AdU for ; Thu, 24 Aug 2017 03:18:02 +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 DB52D5FBEA for ; Thu, 24 Aug 2017 03:18: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 EAE66E0C21 for ; Thu, 24 Aug 2017 03:18: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 3E0F325386 for ; Thu, 24 Aug 2017 03:18:00 +0000 (UTC) Date: Thu, 24 Aug 2017 03:18:00 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-21800) Some services had issue coming up after express upgrade on IOP clusters MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 24 Aug 2017 03:18:05 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139501#comment-16139501 ] Hudson commented on AMBARI-21800: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #50 (See [https://builds.apache.org/job/Ambari-branch-2.6/50/]) AMBARI-21800. Some services had issue coming up after express upgrade on (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9de2499a861c00830d4c28243e992c3182cef8be]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/metadata/RoleCommandOrder.java > Some services had issue coming up after express upgrade on IOP clusters > ----------------------------------------------------------------------- > > Key: AMBARI-21800 > URL: https://issues.apache.org/jira/browse/AMBARI-21800 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.5.2 > Reporter: Siddharth Wagle > Assignee: Siddharth Wagle > Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21800.patch > > > Some services had an issue coming up after express upgrade on IOP clusters. Express upgrade was successful as per Ambari UI. > It seems like something is wrong with RCO post-upgrade where the older stack version RCO gets recached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)