----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45378/#review125620 -----------------------------------------------------------
Ship it! Ship It! - Andrew Onischuk On March 28, 2016, 10:02 a.m., Dmitro Lisnichenko wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/45378/ > ----------------------------------------------------------- > > (Updated March 28, 2016, 10:02 a.m.) > > > Review request for Ambari and Andrew Onischuk. > > > Bugs: AMBARI-15597 > https://issues.apache.org/jira/browse/AMBARI-15597 > > > Repository: ambari > > > Description > ------- > > 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. > > > Diffs > ----- > > > ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/alerts/alert_nodemanager_health.py > 2105bed > > Diff: https://reviews.apache.org/r/45378/diff/ > > > Testing > ------- > > mvn clean test > > > Thanks, > > Dmitro Lisnichenko > >
