[AMBARI-23047] Knox startup attempts fails after Blueprint deployment if HDFS audit is enabled

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.5.1
• Component/s: ambari-admin, ambari-server
• Assignee: Unassigned
• Reporter: Rohit Rai Malhotra
• Created: 22/Feb/18 09:52
• Updated: 22/Feb/18 09:52

Description

While deploying the Blueprint, the Knox service tries to start up before HDFS(Namenode), this works fine when HDFS audit is not enabled.

But Ranger policies are implemented with HDFS audit enabled, the Knox startup fails as Ambari checks for HDFS files & set permission for /ranger/audit etc.

Thus, Ambari needs to handle the case when HDFS audit is enabled but HDFS is not up during Knox startup

OR

The startup sequence should be changed for Knox to start "after" HDFS.