You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2015/02/07 02:54:34 UTC

[jira] [Commented] (AMBARI-9530) After upgrade to 1.7, Ambari is not longer honor ganglia/nagios with https

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

Yusaku Sako commented on AMBARI-9530:
-------------------------------------

+1 for the patch.

> After upgrade to 1.7, Ambari is not longer honor ganglia/nagios with https
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-9530
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9530
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9530.patch
>
>
> PROBLEM: Enable https for ganglia and nagios, then upgrade to Ambari 1.7, after that, although ganglia.https=true is still in ambari.properties, the quick link of ganglia and nagios are both pointing to http. 
> And all the host metrics is lost as well, since Ambari make the curl call to http instead of https. 
> SUPPORT ANALYSIS: 
> As workaround, we have to run ambari-server setup-security to disable the https for both nagios and ganglia.
> Then run ambari-server setup-security again to enable it. 



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