[AMBARI-13321] Oozie Alert Fails In Kerberized Environment That Is Not SSL

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 06/Oct/15 11:05
• Updated: 06/Oct/15 14:23
• Resolved: 06/Oct/15 11:12

Description

The Oozie alert check for the server status (`alert_check_oozie_server.py`) is
not correctly performing a kinit before each check. There are two overall
problems:

• The smokeuser is being used instead of the oozie user
• The principal is using 0.0.0.0 instead of the FQDN of the host.

[root@c6401:~]$ kinit -k -t /etc/security/keytabs/spnego.service.keytab HTTP/c6401.ambari.apache.org
[root@c6401:~]$ oozie admin --oozie http://0.0.0.0:11000/oozie -status
Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of retries = 1. Exception = Could not authenticate, org.apache.hadoop.security.authentication.client.AuthenticationException: Invalid SPNEGO sequence, status code: 400
[root@c6401:~]$ oozie admin --oozie http://c6401.ambari.apache.org:11000/oozie -status
System mode: NORMAL

Issue Links

• links to: ReviewBoard