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

Hadoop QA commented on AMBARI-12635:
------------------------------------

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

This message is automatically generated.

> If the "current" stack version status is OUT_OF_SYNC, no version box is 
> displayed on Admin > Stacks > Version page
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-12635
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12635
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12635.patch
>
>
> Under some circumstances, the current stack version can be in OUT_OF_SYNC 
> state. When this happens, no version box is displayed under Admin > Stacks > 
> Versions, even for the current stack version. Current stack version should 
> always be visible.



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

Reply via email to