Unable to determine service address for namenode nn1

[#1]

in our ambari cluster we see the following

on the first nn1

 $ hdfs haadmin -checkHealth master01 

Illegal argument: Unable to determine service address for namenode 'master01'

on the second namenode

 $ hdfs haadmin -checkHealth master03 

Illegal argument: Unable to determine service address for namenode 'master03'

what could be the problem here ?

and how to debug the command in order to verify what is the root cause ?

remark - DNS configuration on all hosts/IP are right

other example since namenode is down

[hdfs@master01 root]$ hdfs haadmin -transitionToActive --forceactive master01
Illegal argument: Unable to determine service address for namenode 'master01'

[#2]

the hostname is - master01.sys56.com ( i just edit it manual because security issue) this isnt the problem

[#3]

grep dfs.namenode.rpc-address.hdfsha.nn1  /etc/hadoop/conf/hdfs-site.xml 
      <name>dfs.namenode.rpc-address.hdfsha.nn1</name

[#4]

do you see conflict here?

grep -A 3 dfs.ha.namenodes  /etc/hadoop/conf/hdfs-site.xml 
 <name>dfs.ha.namenodes.hdfsha</name> 
      <value>nn1,nn2</value>
    </property>
but:
[hdfs@master01 root]$ hdfs getconf -namenodes
master01.sys56.com master03.sys56.com
[hdfs@master01 root]$

[#5]

@Aditya , the other link ( https://community.hortonworks.com/questions/149951/how-to-force-name-node-to-be-active.html), is about force namenode to active but I just not sure if my problem here is about the same issue , so because that I opened another thread ,

second what we can do next , based on my previous question do you see any conflict ?

[#6]

@Aditya ok , so what we can do next ?