An SAPHana resource returns the wrong primary status for a node when the hdbnsutil -sr_state (or -sr_stateConfiguration) command doesn't respond

Issue

• A message like the following is logged, where node_status does not match the node's true current status, and then Pacemaker initiates a failover.

  ACT: Using getParameter.py as fallback - node_status=<wrong_status>
  *or*
  ACT: hdbnsutil not answering - using global.ini as fallback - node_status=<wrong_status>
  

• Secondary node does not get promoted after SAP HANA binaries are lost on the primary node in a High Availability cluster.

• HANA is in stopped state on both nodes of a Pacemaker cluster after losing the hdb binaries on the primary node.
• When the cluster is in maintenance mode, HANA continues to run on both nodes after the hdb binaries are removed from one node. When the cluster is not in maintenance mode, the SAPHana resource agent takes action to stop the HANA instances.

• An SAPHanaTopology resource logs the following, where srmode does not match the node's true current SR mode.

  ACT: hdbnsutil not answering - using global.ini as fallback - srmode=<wrong_mode>