[AMBARI-14814] Ambari not showing active/standby status for NameNodes when custom ports are used

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2.1
• Fix Version/s: 2.2.2
• Component/s: ambari-server
• Assignee: Vitaly Brodetskyi
• Reporter: Vitaly Brodetskyi
• Created: 27/Jan/16 16:09
• Updated: 01/Feb/16 19:22
• Resolved: 01/Feb/16 16:59

Description

Steps:
Deployed cluster via UI.
Enabled NameNode HA.
Enabled ResourceManager HA.
Changed ports to custom (38088) for "yarn.resourcemanager.webapp.address.rm1" and "yarn.resourcemanager.webapp.address.rm2" properties.
Restarted all services, required it.
Enabled NameNodeHA.
Changed ports to custom (38088) for
dfs.namenode.http-address.nameservice.nn1
dfs.namenode.http-address.nameservice.nn2
dfs.namenode.https-address.nameservice.nn1
dfs.namenode.https-address.nameservice.nn2
dfs.namenode.rpc-address.nameservice.nn1
dfs.namenode.rpc-address.nameservice.nn2
properties.
Restarted all services, required it.
Result: Ambari is not showing which NameNode is active and which one is standby.

Issue Links

• links to: review request