[
https://issues.apache.org/jira/browse/AMBARI-10506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498242#comment-14498242
]
Hadoop QA commented on AMBARI-10506:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12725897/AMBARI-10506.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2361//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2361//console
This message is automatically generated.
> Shore up tactical outages around managing configuration files needed for
> enabling SSL and RPC encryption
> --------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-10506
> URL: https://issues.apache.org/jira/browse/AMBARI-10506
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Erik Bergenholtz
> Assignee: Antonenko Alexander
> Fix For: 2.1.0
>
> Attachments: AMBARI-10506.patch
>
>
> Shore up tactical outages around managing configuration files needed for
> enabling SSL and RPC encryption (ssl-client.xml and ssl-server.xml). This
> will address the first need of just being able to configure everything
> through Ambari. The user still has to know what properties to put where, and
> this is already covered in our doc sets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
