ab-mohamed
commented
2 years ago I have found the following two constraints in the cluster configurations:
location SAPHanaTopology_PRD_HDB00_not_on_majority_maker cln_SAPHanaTopology_PRD_HDB00 -inf: None
location SAPHana_PRD_HDB00_not_on_majority_maker msl_SAPHana_PRD_HDB00 -inf: NoneI did not see anylocation constraints before for HANA scale-Up Perf-Opt HA.
@yeoldegrove Can you please check the cluster configurations? I believe there are some added configurations in the last release. Maybe during the scale-out architecture testing?
yeoldegrove
Used cloud platform GCP Used SLES4SAP version SLSES 15 SP3 for SAP Applciations
Used client machine OS macOS 13.4
Expected behaviour vs observed behaviour I expected that HANA would start successfully using the SAPHana resource agent, but it did not work
How to reproduce
Use the most recent
masterbranch to deploy HANA (2.0 SPS05) HA using theterraform apply --auto-approvecommand.HANA DB did not work on
ab-vmhana01host, and the HSR failed:Node List:
Inactive Resources:
Migration Summary:
Failed Resource Actions:
ab-vmhana02:~ # SAPHanaSR-showAttr perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE = "UTF-8", LANG = (unset) are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). Global cib-time
global Wed Jun 1 08:04:53 2022
Resource is-managed
cln_SAPHanaTopology_PRD_HDB00 true
Sites srHook
FRA PRIM
Hosts clone_state lpa_prd_lpt node_state op_mode remoteHost roles score site srmode sync_state version vhost
ab-vmhana01 UNDEFINED 10 online logreplay ab-vmhana02 1:P:master1::worker: -9000 NUE sync SFAIL 2.00.052.00.1599235305 ab-vmhana01 ab-vmhana02 PROMOTED 1654070693 online logreplay ab-vmhana01 4:P:master1:master:worker:master 150 FRA sync PRIM 2.00.052.00.1599235305 ab-vmhana02
ab-vmhana02:~ # su - prdadm prdadm@ab-vmhana02:/usr/sap/PRD/HDB00> HDBSettings.sh systemReplicationStatus.py; echo RC:$? there are no secondary sites attached
Local System Replication State
mode: PRIMARY site id: 1 site name: NUE RC:15
prdadm@ab-vmhana01:/usr/sap/PRD/HDB00> hdbnsutil -sr_stateConfiguration --sapcontrol=1 SAPCONTROL-OK:
mode=primary
site id=1
site name=NUE
SAPCONTROL-OK:
done.
prdadm@ab-vmhana02:/usr/sap/PRD/HDB00> hdbnsutil -sr_stateConfiguration --sapcontrol=1 SAPCONTROL-OK:
mode=sync
site id=2
site name=FRA
active primary site=1
primary masters=ab-vmhana01
SAPCONTROL-OK:
done.
prdadm@ab-vmhana02:/usr/sap/PRD/HDB00> HDB stop prdadm@ab-vmhana01:/usr/sap/PRD/HDB00> HDB stop
ab-vmhana01:~ # rpm -qa | grep SAPHanaSR-0 SAPHanaSR-0.155.0-4.17.1.noarch
ab-vmhana01:~ # zypper in --oldpackage SAPHanaSR-0.154.1-4.14.1 ab-vmhana02:~ # zypper in --oldpackage SAPHanaSR-0.154.1-4.14.1
ab-vmhana01:~ # crm cluster start ab-vmhana02:~ # crm cluster start
ab-vmhana01:~ # crm_mon -rnf1 Cluster Summary:
Node List:
Inactive Resources:
Migration Summary:
Failed Resource Actions:
ab-vmhana01:~ # journalctl -f -u pacemaker -u corosync […] Jun 01 08:34:14 ab-vmhana01 pacemaker-schedulerd[25531]: warning: Unexpected result (not running) was recorded for start of rsc_SAPHana_PRD_HDB00:0 on ab-vmhana01 at Jun 1 08:32:21 2022 Jun 01 08:34:14 ab-vmhana01 pacemaker-schedulerd[25531]: warning: Unexpected result (not running) was recorded for start of rsc_SAPHana_PRD_HDB00:0 on ab-vmhana01 at Jun 1 08:32:21 2022 Jun 01 08:34:14 ab-vmhana01 pacemaker-schedulerd[25531]: warning: Forcing msl_SAPHana_PRD_HDB00 away from ab-vmhana01 after 1000000 failures (max=5000) Jun 01 08:34:14 ab-vmhana01 pacemaker-schedulerd[25531]: warning: Forcing msl_SAPHana_PRD_HDB00 away from ab-vmhana01 after 1000000 failures (max=5000)
Used terraform.tfvars