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

Hadoop QA commented on AMBARI-19235:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844243/AMBARI-19235.3.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest

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

This message is automatically generated.

> 'Cluster User' role issue after Ambari 2.4.2.0 upgrade
> ------------------------------------------------------
>
>                 Key: AMBARI-19235
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19235
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.2
>            Reporter: Eugene Chekanskiy
>            Assignee: Eugene Chekanskiy
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19235.2.patch, AMBARI-19235.3.patch, 
> AMBARI-19235.patch
>
>
> After upgrading from Ambari 2.4.0.1 to Ambari 2.4.2, something has changed 
> that breaks role based access control. Users in the "Cluster User" role no 
> longer get access to the views as they could in 2.4.0.



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

Reply via email to