[jira] [Commented] (AMBARI-14157) NN HA HDFS service check failed because NameNode was in the SafeMode

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-14157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036363#comment-15036363 ] 

Hudson commented on AMBARI-14157:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #988 (See [https://builds.apache.org/job/Ambari-branch-2.1/988/])
AMBARI-14157 NN HA HDFS service check failed because NameNode was in the (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=67e4f25497501bfa481f753e4bd878b778662f2e])
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py


> NN HA HDFS service check failed because NameNode was in the SafeMode
> --------------------------------------------------------------------
>
>                 Key: AMBARI-14157
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14157
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.1.3
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-14157.patch
>
>
> On Start Services during Kerberization HDFS Check failed because NN was in the SafeMode
> NN was active, but when we were waiting to leave safe mode:We waited for another NN to exit safe mode, which is not active.
> It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode state for both NN, not only for the current



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