ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-12351) SecondaryNameNode alert not working with SPNEGO enabled cluster
Date Thu, 09 Jul 2015 10:34:05 GMT
Andrew Onischuk created AMBARI-12351:
----------------------------------------

             Summary: SecondaryNameNode alert not working with SPNEGO enabled cluster
                 Key: AMBARI-12351
                 URL: https://issues.apache.org/jira/browse/AMBARI-12351
             Project: Ambari
          Issue Type: Bug
            Reporter: Andrew Onischuk
            Assignee: Andrew Onischuk
             Fix For: 2.1.0


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.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message