You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/08/24 03:18:00 UTC

[jira] [Commented] (AMBARI-21800) Some services had issue coming up after express upgrade on IOP clusters

    [ 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)