Upgrade fails with Ranger error, Namenode not able to start

[#1]

SYMPTOM: During an upgrade to Ambari 2.1.2 and HDP 2.3.2 the upgrade fails when trying to start the namenode service. Errors in the stack trace indicate that the xasecure files are not found.

ISSUE: When Ranger has been installed outside of Ambari, the method used for previous HDP versions, the Ambari database does not contain information about Ranger. As a result the configuration files are not replicated to the new directory structure, /etc/hadoop/<version>/0/. Since the Ranger properties are included in other component configuration files the namenode service will not start. A result of the missing configuration files for Ranger.

RESOLUTION: If Ranger was installed outside of Ambari you can replicate the xasecure files from the previous version to the current version configuration directory.

cp /etc/hadoop/conf/xasecure* /etc/hadoop/<version>/0/ 
ie. cp /etc/hadoop/conf/xasecure* /etc/hadoop/2.3.2.0-2950/0/

** You will need to complete this on all namenode servers in the cluster After you complete this you will be able to start the nameservice using the following command.

/usr/hdp/current/hadoop-client/sbin/hadoop-daemon.sh start namenode

This will allow you to continue the upgrade process.