[
https://issues.apache.org/jira/browse/AMBARI-20193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883947#comment-15883947
]
Hadoop QA commented on AMBARI-20193:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854624/AMBARI-20193.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-logsearch/ambari-logsearch-portal.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10753//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10753//console
This message is automatically generated.
> Log Search Portal is not working with HTTPS with it's own created Key Store
> ---------------------------------------------------------------------------
>
> Key: AMBARI-20193
> URL: https://issues.apache.org/jira/browse/AMBARI-20193
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.5.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20193.patch
>
>
> If "Advanced logsearch-env / Log Search UI Protocol" is set to https and we
> let Log Search to create it's own Key Store than it's not working fine, the
> service starts but the portal is unavailable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
