What were you trying to do that didn't work?

Specify corner-case values of timeout of command pcs status wait. Two cases can be adjusted:

• Zero timeout values: solved in RHEL-44719
• Upper timeout boundary

This was found as a part of RHEL-25854 verification, for full verification see this comment.

Please provide the package NVR for which the bug is seen:

pcs-0.11.7-3.el9

How reproducible is this bug?:

always

Steps to reproduce

Upper timeout boundary - the command will automatically produce error, if high timeout is entered. The boundary starts somewhere around 900000000s, the error is not present with 800000000s.

[root@virt-242 ~]# pcs status wait 900000000s
Waiting for the cluster to apply configuration changes (timeout: 900000000 seconds)...
Error: waiting timeout
crm_resource: Error performing operation: Timeout occurred
Pending actions:
[root@virt-242 ~]# echo $?
1