Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 19 Sep 2017 22:46:00 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13100921.1504905124000.151788.1505861160294@Atlassian.JIRA>
In-Reply-To: <JIRA.13100921.1504905124000@Atlassian.JIRA>
References: <JIRA.13100921.1504905124000@Atlassian.JIRA> <JIRA.13100921.1504905124932@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AMBARI-21917) 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
archived-at: Tue, 19 Sep 2017 22:46:05 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172467#comment-16172467 ] 

Hudson commented on AMBARI-21917:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #248 (See [https://builds.apache.org/job/Ambari-branch-2.6/248/])
AMBARI-21917. 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=3e8ba2a1f1b4bc8d4152492cf2fd65895111d926])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/metadata/CachedRoleCommandOrderProvider.java


> Some services had issue coming up after express upgrade on IOP clusters
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-21917
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21917
>             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-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded. However, certain test environments have reported seeing incorrect / older RCO still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701  INFO [Server Action Executor Worker 1509] StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to for re-creation of RCO.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)