[
https://issues.apache.org/jira/browse/AMBARI-16245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270442#comment-15270442
]
Hadoop QA commented on AMBARI-16245:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12802140/AMBARI-16245.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6774//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6774//console
This message is automatically generated.
> Cluster User should not have access to component logs
> -----------------------------------------------------
>
> Key: AMBARI-16245
> URL: https://issues.apache.org/jira/browse/AMBARI-16245
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-16245.patch
>
>
> {quote}
> Native UI Integrations: Ambari needs to be able to provide the following UI
> integrations for users with SERVICE_OPERATOR role and above:
> {quote}
> Hide the component logs from Host Details > Logs tab.
> Rather than hiding the component logs from the Background Op Popup, I'm
> wondering if we should hide background ops altogether for CLUSTER USER since
> they cannot do any operations anyway.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
