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

Hudson commented on AMBARI-9530:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #1713 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1713/])
AMBARI-9530. After upgrade to 1.7, Ambari is not longer honor ganglia/nagios 
with https (jaimin via srimanth) (sgunturi: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b9a06522ef07bb5216a04575aabb5d251d9097ab)
* ambari-web/app/views/common/quick_view_link_view.js
* ambari-web/test/views/common/quick_link_view_test.js


> 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)

Reply via email to