ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9081) Rolling Upgrades: clients do not send information about their version on restart
Date Thu, 15 Jan 2015 00:12:34 GMT

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

Hadoop QA commented on AMBARI-9081:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12692359/AMBARI-9081.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 2 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/1329//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1329//console

This message is automatically generated.

> Rolling Upgrades: clients do not send information about their version on restart
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-9081
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9081
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9081.patch
>
>
> See AMBARI-8995, after that changes master components have their version in the results
of START command, but clients do not execute this command and thus it's not possible to track
their new version. As the result some components of the cluster remain in non upgraded state
and it prevents from setting cluster to upgraded state and finalize upgrade.



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

Mime
View raw message