Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 7 Feb 2015 01:45:34 +0000 (UTC)
From: "Srimanth Gunturi (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12773184.1423273483000.288744.1423273534396@Atlassian.JIRA>
In-Reply-To: <JIRA.12773184.1423273483000@Atlassian.JIRA>
References: <JIRA.12773184.1423273483000@Atlassian.JIRA>
 <JIRA.12773184.1423273483698@arcas>
Subject: [jira] [Created] (AMBARI-9530) After upgrade to 1.7, Ambari is not
 longer honor ganglia/nagios with https
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Srimanth Gunturi created AMBARI-9530:
----------------------------------------

             Summary: 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


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)