HANA nodes end up having the same LPT values

Often, there are cases when cluster can not pick up on primary/ secondary roles.
Cluster tries to register the primary node as secondary, and the secondary node as primary.
The reason for it is due to manually switching roles of primary to secondary, and vice versa while cluster is in maintenance.
By that, cluster attributes get outdated, and cluster can not pick up the right roles when removed from maintenance.

Such a situation could be clearly seen using crm_mon -A1 command, where cluster nodes end up having the same LPT values, and hana_***_clone_state have values UNDEFINED, WAITING4PRIM, WAITING4REG

crm_mon -Ar command shows the below output...

# crm_mon -Ar 
...
Node List:
  * Online: [ node1 node2 ]
...
Node Attributes:
  * Node: node1:
    * hana_fu2_clone_state              : UNDEFINED 
...
    * lpa_fu2_lpt                       : 10
    * master-rsc_SAPHana_FU2_HDB02      : -9000
  * Node: node2:
    * hana_fu2_clone_state              : WAITING4PRIM
 ...
    * lpa_fu2_lpt                       : 10
    * master-rsc_SAPHana_FU2_HDB02      : -INFINITY

Please follow the below steps to resolve the issue...

1. On either node bring the msl* resource into maintenance, and make ensure that the it shows as "unmanaged":
# crm resource maintenance msl_* on
# crm_mon -1r

2. Ensure cluster is in idle state:
# cs_wait_for_idle -s 5
Cluster state: S_IDLE

3. Start HANA manually on both nodes (if not already started) and ensure replication is working...

3.1 On primary node check HANA status HostConfig and Replication status:
# sapcontrol -nr ** -function GetProcessList: echo RC:$?
# HDBsettings.sh systemReplicationStatus.py; echo RC:$?
# HDBsettings.sh landscapeHostConfiguration.py; echo RC:$?

4. If all looks fine, then proceed refreshing msl_* resource and bring it out of maintenance:
# cs_clusterstate -i
# crm resource refresh msl_*
# crm resource maintenance msl_* off

5. Check the cluster status, ensure that all resources are running, and that cluster correctly picks up the primary/ secondary roles:
# SAPHanaSR-showAttr
# crm_mon -1r
# cs_clusterstate -i

2) Recommended tool for showing the status of SAPHanSR
cluster and HANA database is SAPHanaSR-showAttr.

See manual pages SAPHanaSR_maintenance_examples(7),
SAPHanaSR-showAttr(8).

See also respective sections in setup guide, e.g.
- https://documentation.suse.com/sbp/all/single-html/SLES4SAP-hana-sr-guide-PerfOpt-15/#id-saphanasr-command-line-tools
- https://documentation.suse.com/sbp/all/single-html/SLES4SAP-hana-sr-guide-PerfOpt-15/#id-migrating-an-sap-hana-primary

See also blog articles on #towardszerodowntime, e.g.
- https://www.suse.com/c/sap-hana-maintenance-suse-clusters/
- https://www.suse.com/c/sles-for-sap-hana-maintenance-procedures-part-2-manual-administrative-tasks-os-reboots-and-updation-of-os-and-hana/