deploying oozie and hive with namenode ha via ambari blueprint

[#1]

on a cluster deployed via Ambari blueprint with namenode ha, hbase is able to resolve the dfs.nameservices and finds the right namenode , where us hive and oozie fails with the following error:

HDP VERSION: 2.4.2

Error: java.net.UnknownHostException: HDP1

Stack trace for the error was (for debug purposes):
--------------------------------------
java.lang.IllegalArgumentException: java.net.UnknownHostException: HDP1
    at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:411)
    at org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
    at org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
    at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:678)
    at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:619)
    at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:150)
    at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2653)
    at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:92)
    at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2687)
    at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2669)
    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:371)
    at org.apache.oozie.service.HadoopAccessorService$4.run(HadoopAccessorService.java:513)
    at org.apache.oozie.service.HadoopAccessorService$4.run(HadoopAccessorService.java:511)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:422)<br>

Appreciate any suggestions, help

[#2 · Accepted solution]

soln: the solution is to install HDFS_CLIENT on the hive node, that way core-site.xml will be present and hence hive can use the dfs.nameservice config property