You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/11/24 15:54:11 UTC

[jira] [Commented] (AMBARI-14041) RU: Downgrade does not restart failed service component

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

Hadoop QA commented on AMBARI-14041:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12774070/AMBARI-14041.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4382//console

This message is automatically generated.

> RU: Downgrade does not restart failed service component
> -------------------------------------------------------
>
>                 Key: AMBARI-14041
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14041
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-14041.patch
>
>
> Downgrade orchestration will skip components that are on the version that is being targeted for download.  This approach works if the failing component has advertised the newer version, but not if it still advertises the old version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)