[
https://issues.apache.org/jira/browse/AMBARI-15597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214564#comment-15214564
]
Hudson commented on AMBARI-15597:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4550 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4550/])
AMBARI-15597. After enabling SSL for Resource Manager, getting a (dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d0672c2ba8d1f8a15ae58c6af62f62f7edc47466])
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/alerts/alert_nodemanager_health.py
> After enabling SSL for Resource Manager, getting a constant Ambari Alert:
> Connection failed to https://0.0.0.0:8044/ws/v1/node/info (No JSON object
> could be decoded)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-15597
> URL: https://issues.apache.org/jira/browse/AMBARI-15597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.2
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.2.2
>
> Attachments: AMBARI-15597.patch
>
>
> Enabled SSL for ResourceManager HA.
> The following parameter changed in yarn-site.xml
> <name>yarn.nodemanager.webapp.https.address</name>
> <value>0.0.0.0:8044</value>
> After implementing SSL, they started getting the following Ambari Alert from
> all the nodes.
> Connection failed to https://0.0.0.0:8044/ws/v1/node/info (No JSON object
> could be decoded)
> We tested the Python socket.getfqdn() inside the alert_nodemanager_health.py
> and it worked correctly.
> print socket.getfqdn("0.0.0.0")
> CAUSE:
> We think that Kerberos looks for the yarn.nodemanager.webapp.https.address
> hostname in yarn-site.xml and because it sees “0.0.0.0” instead of the
> hostname, it can’t get the keytabs of the host.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
