[AMBARI-24893] Add relevant NameNode start logic to OneFS mpack

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.0

Environment

HDP 3.0.1 + OneFS 8.1.2

• Assignee: Unassigned
• Reporter: David Tucker
• Created: 13/Nov/18 23:21
• Updated: 04/Dec/18 13:26

Description

Deploying with OneFS using the mpack seems to omit setup steps. I'm not sure exactly where the steps are defined in 2.7, but in 2.6 they seem to be here:
https://github.com/apache/ambari/blob/ac651d9d88d0c65d7ec1141ac5cd2af659781d79/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py#L102-L238

It's possible not all the steps are relevant, but at the very least these seem to be:
https://github.com/apache/ambari/blob/ac651d9d88d0c65d7ec1141ac5cd2af659781d79/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py#L234-L235

According to Kiran, "this is causing issue starting some of the services and importantly timeline server V2 is unable to create necessary znode and start ats-hbase app."

It also appears to cause the YARN service check to fail with an ACE (since /user/ambari-qa was not set up correctly).