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

Hadoop QA commented on AMBARI-15243:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12790708/AMBARI-15243.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-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5647//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5647//console

This message is automatically generated.

> Message for Ambari admin user isn't displayed in User Settings popup
> --------------------------------------------------------------------
>
>                 Key: AMBARI-15243
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15243
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15243.patch, admin-message.jpg, 
> no-admin-message.jpg
>
>
> User Settings popup contains information about user roles. If user is Ambari 
> admin, the appropriate [information message|^admin-message.jpg] should be 
> displayed. [Cluster roles table|^no-admin-message.jpg] is displayed, in case 
> when ambari admin logs in first time. Page refresh solves this issue.



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

Reply via email to