[
https://issues.apache.org/jira/browse/AMBARI-13565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974947#comment-14974947
]
Hudson commented on AMBARI-13565:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #748 (See
[https://builds.apache.org/job/Ambari-branch-2.1/748/])
AMBARI-13565. Oozie alert appears after enabling NN HA, moving NameNode
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2f41cc67e5c109af66275c9f61813abd9937856b])
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/alerts/alert_check_oozie_server.py
> Oozie alert appears after enabling NN HA, moving NameNode and enabling
> security
> -------------------------------------------------------------------------------
>
> Key: AMBARI-13565
> URL: https://issues.apache.org/jira/browse/AMBARI-13565
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Steps:
> 1. Deploy cluster.
> 2. Enable NameNode HA.
> 3. Move NameNode to another host.
> 4. Enable Security.
> Result: Oozie has CRIT "Oozie Server Status" alerts, appearing and
> disappearing with period about 5 minutes. Message of alert:
>
>
>
> Execution of 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ;
> oozie admin -oozie http://ambari-us-rhe6-haenabling-2.novalocal:11000/oozie
> -status' returned 255. Error: IO_ERROR : java.io.IOException: Error while
> connecting Oozie server. No of retries = 1. Exception = Could not
> authenticate, GSSException: No valid credentials provided (Mechanism level:
> Ticket expired (32))
>
> Cluster: <http://172.22.89.94:8080/>, lifetime: +120h.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)