[
https://issues.apache.org/jira/browse/AMBARI-15370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189976#comment-15189976
]
Hadoop QA commented on AMBARI-15370:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12792512/AMBARI-15370.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/5816//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5816//console
This message is automatically generated.
> Login as regular user (no cluster access at all) but background ops are
> running about cluster
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-15370
> URL: https://issues.apache.org/jira/browse/AMBARI-15370
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15370.patch, user-running-ui (4).tiff
>
>
> I created a local user and did not give them access to any cluster.
> Logged in and notice that Ambari Web is making calls to backend about cluster
> items (hosts, alerts, etc).
> The calls come back 403 since this user doesn't have access to cluster
> resources but these calls are not necessary overhead, and in case of real
> problems, errors like this will confuse real errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
