[
https://issues.apache.org/jira/browse/AMBARI-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165877#comment-14165877
]
Hadoop QA commented on AMBARI-7717:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673997/AMBARI-7717.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/137//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/137//console
This message is automatically generated.
> Upgrade: Admin gets unnecessary READ permissions
> ------------------------------------------------
>
> Key: AMBARI-7717
> URL: https://issues.apache.org/jira/browse/AMBARI-7717
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Priority: Critical
> Fix For: 1.7.0, 2.0.0
>
> Attachments: AMBARI-7717.patch, after-170-upgrade.tiff, prior-161.tiff
>
>
> During upgrade to Ambari 1.7.0, local users and admins get migrated fine,
> however, Ambari is explicitly giving CLUSTER.READ to admins.
> The admins really don't need this READ, they just need CLUSTER.OPERATE (which
> they already have).
> See attachment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
