"SAPHanaSR-monitor" command always show "yellow" status even though the HANA Cluster is healthy

SUSE Linux Enterprise Server for SAP Applications 15 SP6

The HANA Scale-up Cluster is setup using the classical "SAPHanaSR".
The "SAPHanaSR-monitor" command always show "yellow" status even though the HANA Cluster is healthy.
   
For example:

# /usr/sbin/SAPHanaSR-monitor
=========== Wed May 21 15:19:21 2025 ================
OVERALL:   HA1: yellow                   Wed May 21 15:19:42 CST 2025

SR:        green suse01 => suse02

Cluster:   yellow ( C#n)
HANA1:     suse01 green
HANA2:     suse02 green

SAPHanaSR: green ()
LPA:       green (LPA: GREEN)
LPA:       suse01 1747811961
LPA:       suse02 30

Syslog:    green ()

RETURN_CODE: 0

Engineering is aware of this bug and is currently working on a fix.
If a patch is required urgently, please open a Support Case to request for a PTF.

The "SAPHanaSR-monitor" command is not fully compatible with the new Pacemaker 2.1.7 (used by SLE15 SP6 HA) due to some changes in the CIB specification.
The "crmd" attribute value (in the "node_state" element) is now a "epoch time" instead of either "online" or "offline" as stated in the new specification.

https://clusterlabs.org/projects/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/index.html#node-state

15.1. Node State
Attributes of a node_state Element

Name     Type                                                    Description

in_ccm   epoch time (since 2.1.7; previously boolean)            If the node’s controller is currently in the cluster layer’s membership, this is the epoch time at which it joined (or 1 if the node is in the process of leaving the cluster), otherwise 0
                                                                 (since 2.1.7; previously, it was “true” or “false”)
crmd     epoch time (since 2.1.7; previously an enumeration)     If the node’s controller is currently in the cluster layer’s controller messaging group, this is the epoch time at which it joined, otherwise 0
                                                                 (since 2.1.7; previously, the value was either “online” or “offline”)