[
https://issues.apache.org/jira/browse/AMBARI-16268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278338#comment-15278338
]
Hadoop QA commented on AMBARI-16268:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12803246/AMBARI-16268.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/6815//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6815//console
This message is automatically generated.
> "Open In Log Search" link goes back to the Ambari dash board
> ------------------------------------------------------------
>
> Key: AMBARI-16268
> URL: https://issues.apache.org/jira/browse/AMBARI-16268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16268.patch, Screen Shot 2016-05-01 at 1.39.41 PM
> (1).png
>
>
> See attached image. Clicking on the link takes you to the dashboard. I assume
> it is expected to take the user to LogSearch UI and there we do not have an
> SSO solution. So user has to put in own credential again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
