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

Hadoop QA commented on AMBARI-8313:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12681370/AMBARI-8313.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 3 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-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/634//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/634//console

This message is automatically generated.

> Remove Nagios SSL Configuration From Ambari Scripts
> ---------------------------------------------------
>
>                 Key: AMBARI-8313
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8313
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8313.patch
>
>
> When Nagios was a part of the Ambari ecosystem, it was required that Ambari 
> trusted the SSL connection with Nagios. This was configured via the 
> {{ambari-server setup-security}} command.
> Now that Nagios has been removed, trusting SSL connections is no longer 
> necessary and this setup option should be removed.



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

Reply via email to