post the pcs colocation and ordering constraint the resource gets stopped and does not start in Rocky9

pcs-0.11.9-2.el9_6.2.x86_64
pacemaker-2.1.9-1.2.el9_6.x86_64
corosync-3.1.9-2.el9_6.x86_64

Will the above versions installed in Rocky9 VM, the following are the configurations

--------------------------------
pcs resource create resource_one ocf:test:rest_healthcheck url=http://localhost:1990/api/status meta failure-timeout=15 op monitor interval=1s
pcs resource clone resource_one globally-unique=false clone-node-max=1 meta failure-timeout=15 migration-threshold=3

pcs resource create resource_two ocf:heartbeat:IPaddr2 ip={resource_two_ipv4} cidr_netmask={resource_two_subnet_ipv4} nic=eth0 meta failure-timeout=15 op monitor interval=5s
pcs resource disable resource_two
pcs resource cleanup resource_two

if resource_two_ipv4 pcs constraint colocation add resource_two with resource_one-clone INFINITY
if resource_two_ipv4 pcs constraint order start resource_one-clone then start resource_two kind=Mandatory

pcs resource enable resource_two

--------------------------------

The cluster consists of 3 nodes, vm0, vm1, vm2.

The expectation is that when resource_one-clone is started on vm0, then the resource_two should also be started on vm0.
But we see that resource_two is not getting started.

The same configuration used to work on Rocky8.
This issue is faced only in Rocky9.

Can you please suggest on what could cause this behavioral change between Rocky8 and Rocky9 when the configurations are same.

Other details:

pcs constraint config --all
Colocation Constraints:
resource 'resource_two' with resource 'resource_one-clone'
score=INFINITY
Order Constraints:
start resource 'resource_one-clone' then start resource 'resource_two'
kind=Mandatory

pcs resource config
Resource: resource_two (class=ocf provider=heartbeat type=IPaddr2)
Attributes: resource_two-instance_attributes
cidr_netmask=25
ip=1.4.2.3
nic=eth0
Meta Attributes: resource_two-meta_attributes
failure-timeout=15
Operations:
monitor: resource_two-monitor-interval-5s
interval=5s
start: resource_two-start-interval-0s
interval=0s timeout=20s
stop: resource_two-stop-interval-0s
interval=0s timeout=20s
Clone: resource_one-clone
Meta Attributes: resource_one-clone-meta_attributes
clone-node-max=1
failure-timeout=15
globally-unique=false
migration-threshold=3
Resource: resource_one (class=ocf provider=test type=rest_healthcheck)
Attributes: resource_one-instance_attributes
url=http://localhost:1990/api/status
Meta Attributes: resource_one-meta_attributes
failure-timeout=15
Operations:
monitor: resource_one-monitor-interval-1s
interval=1s
start: resource_one-start-interval-0s
interval=0s timeout=1
stop: resource_one-stop-interval-0s
interval=0s timeout=1