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

Hadoop QA commented on AMBARI-14340:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12776956/AMBARI-14340.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/4570//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/4570//console

This message is automatically generated.

> Logging into Ambari UI when user only has access to views causes browser to 
> cycle between login page and loading screen
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14340
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14340
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.3.0
>            Reporter: Richard Zang
>            Assignee: Richard Zang
>             Fix For: 2.3.0
>
>         Attachments: AMBARI-14340.patch
>
>
> Logging into Ambari UI when user only has access to views causes browser to 
> cycle between login page and loading screen. The cause for this appears to be 
> a 403 status from the following REST API call. Which appears to only occur if 
> the user has access to multiple views. Haver access to only one view does not 
> exhibit this behavior.



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

Reply via email to