[AMBARI-12351] SecondaryNameNode alert not working with SPNEGO enabled cluster

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 09/Jul/15 10:33
• Updated: 09/Jul/15 12:38
• Resolved: 09/Jul/15 10:42

Description

The Secondary NameNode Process alert fails with a 401 after enabling SPNEGO:
<http://dev.hortonworks.com.s3.amazonaws.com/HDPDocuments/Ambari-Trunk/bk_Amba
ri_Security_Guide/content/_configuring_http_authentication_for_HDFS_YARN_MapRe
duce2_HBase_Oozie_Falcon_and_Storm.html> on a 2.2.6 GA stack with Ambari
2.1.0-1377

[root@revo1 keytabs]# ambari-server --hash
069a34cedf035cbfd5a6ace0f2a113c69f60a5ec
[root@revo1 keytabs]# rpm -q ambari-server
ambari-server-2.1.0-1377.x86_64

http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.2.6.0
http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.20/repos/centos6

Without NN HA enabled, the secondary NN process alert fires with a 401. It
looks like it's not using negotiate to check the state.

Issue Links

• links to: ReviewBoard