Errata Tool added a comment - 2024/04/30 9:32 AM Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Moderate: pcs security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:2113

Steven Levine added a comment - 2024/01/03 5:59 PM mlisik@redhat.com : Do you think this bug fix requires a release note? It seems as though from the user's perspective it's just a better error message.

Michal Mazourek added a comment - 2024/01/02 3:08 PM BEFORE: [root@virt-517 ~]# rpm -q pcs pcs-0.11.6-3.el9.x86_64   [root@virt-517 ~]# pcs resource create test ocf:pacemaker:Dummy op monitor interval= Traceback (most recent call last):   File "/usr/sbin/pcs" , line 33, in <module>     sys.exit(load_entry_point( 'pcs==0.11.6' , 'console_scripts' , 'pcs' )())   File "/usr/lib/python3.9/site-packages/pcs/app.py" , line 271, in main     routing.create_router(cmd_map, [])(   File "/usr/lib/python3.9/site-packages/pcs/cli/common/routing.py" , line 33, in _router     return cmd_map[sub_cmd](lib, argv_next, modifiers)   File "/usr/lib/python3.9/site-packages/pcs/cli/common/routing.py" , line 33, in _router     return cmd_map[sub_cmd](lib, argv_next, modifiers)   File "/usr/lib/python3.9/site-packages/pcs/resource.py" , line 750, in resource_create     lib.resource.create(   File "/usr/lib/python3.9/site-packages/pcs/cli/common/lib_wrapper.py" , line 89, in decorated_run     return run_with_middleware(run, cli_env, *args, **kwargs)   File "/usr/lib/python3.9/site-packages/pcs/cli/common/middleware.py" , line 14, in run     return next_in_line(env, *args, **kwargs)   File "/usr/lib/python3.9/site-packages/pcs/cli/common/middleware.py" , line 42, in apply     result_of_next = next_in_line(env, *args, **kwargs)   File "/usr/lib/python3.9/site-packages/pcs/cli/common/middleware.py" , line 80, in apply     result_of_next = next_in_line(env, *args, **kwargs)   File "/usr/lib/python3.9/site-packages/pcs/cli/common/lib_wrapper.py" , line 80, in run     lib_call_result = run_library_command(lib_env, *args, **kwargs)   File "/usr/lib/python3.9/site-packages/pcs/lib/commands/resource.py" , line 433, in create     primitive_element = resource.primitive.create(   File "/usr/lib/python3.9/site-packages/pcs/lib/cib/resource/primitive.py" , line 232, in create     return append_new(   File "/usr/lib/python3.9/site-packages/pcs/lib/cib/resource/primitive.py" , line 290, in append_new     create_operations(   File "/usr/lib/python3.9/site-packages/pcs/lib/cib/resource/operations.py" , line 396, in create_operations     append_new_operation(operations_element, id_provider, operation)   File "/usr/lib/python3.9/site-packages/pcs/lib/cib/resource/operations.py" , line 426, in append_new_operation     options[ "interval" ], KeyError: 'interval' [root@virt-517 ~]# echo $? 1   AFTER: [root@virt-004 ~]# rpm -q pcs pcs-0.11.6-6.el9.x86_64   Checking if traceback is present with empty value of interval and timeout monitor operation [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op monitor interval= Error: '' is not a valid interval value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# echo $? 1 > OK: An accurate error message is present instead of the traceback [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op monitor timeout= Error: '' is not a valid timeout value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# echo $? 1 > OK Checking various other operations of ocf:pacemaker:Dummy resource (start, stop, migrate_to) [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op start interval= Error: '' is not a valid interval value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op start timeout= Error: '' is not a valid timeout value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op stop interval= Error: '' is not a valid interval value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op stop timeout= Error: '' is not a valid timeout value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op migrate_to interval= Error: '' is not a valid interval value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Dummy op migrate_to timeout= Error: '' is not a valid timeout value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue > OK Checking role option with monitor operation for Stateful resource [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Stateful op monitor role= Error: '' is not a valid role value, use ' Master ', ' Promoted ', ' Slave ', ' Started ', ' Stopped ', ' Unpromoted' Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# echo $? 1 > OK Checking various other options for monitor operation [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Stateful op monitor enabled= Error: '' is not a valid enabled value, use a pacemaker boolean value: ' 0 ', ' 1 ', ' false ', ' n ', ' no ', ' off ', ' on ', ' true ', ' y ', ' yes' Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# echo $? 1 [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Stateful op monitor on-fail= Error: '' is not a valid on-fail value, use ' block ', ' demote ', ' fence ', ' ignore ', ' restart ', ' restart-container ', ' standby ', ' stop' Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# echo $? 1 [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Stateful op monitor id= Error: operation id cannot be empty Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# echo $? 1 Checking invalid operation option [root@virt-004 ~]# pcs resource create test ocf:pacemaker:Stateful op start invalid= Error: invalid resource operation option 'invalid' , allowed options are: 'OCF_CHECK_LEVEL' , 'description' , 'enabled' , 'id' , 'interval' , 'interval-origin' , 'name' , 'on-fail' , 'record-pending' , 'role' , 'start-delay' , 'timeout' Error: Errors have occurred, therefore pcs is unable to continue [root@virt-004 ~]# echo $? 1 > OK Checking that the operation option functionality was preserved [root@virt-004 cli]# pcs resource create test ocf:pacemaker:Dummy op monitor timeout=11 [root@virt-004 cli]# pcs resource config test | grep monitor -A 1     monitor: test-monitor-interval-60s       interval=60s timeout=11 [root@virt-004 cli]# pcs resource create test2 ocf:pacemaker:Dummy op monitor timeout=11s [root@virt-004 cli]# pcs resource config test2 | grep monitor -A 1     monitor: test2-monitor-interval-60s       interval=60s timeout=11s [root@virt-004 cli]# pcs resource create test3 ocf:pacemaker:Dummy op monitor timeout=1m [root@virt-004 cli]# pcs resource config test3 | grep monitor -A 1     monitor: test3-monitor-interval-60s       interval=60s timeout=1m [root@virt-004 cli]# pcs resource config test4 | grep monitor -A 1     monitor: test4-monitor-interval-50       interval=50 > OK Verified for pcs-0.11.6-6.el9.

Michal Mazourek added a comment - 2023/11/27 3:31 PM Tests for preliminary testing were run and examined for pcs-0.11.6-6.el9.

Michal Pospisil added a comment - 2023/11/24 12:36 PM DevTestResults: [root@r09-04-a ~]# rpm -q pcs pcs-0.11.6-6.el9.x86_64 [root@r09-04-a ~]# pcs resource create d-01 ocf:pacemaker:Dummy op monitor interval= Error: '' is not a valid interval value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue [root@r09-04-a ~]# pcs resource create d-01 ocf:pacemaker:Dummy op monitor timeout= Error: '' is not a valid timeout value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue

gitlab-bot added a comment - 2023/11/23 3:28 PM Michal Pospíšil mentioned this issue in a commit of Red Hat / centos-stream / rpms / pcs on branch c9s : pcs-0.11.6-6

gitlab-bot added a comment - 2023/11/21 7:02 PM Michal Pospíšil mentioned this issue in a merge request of Red Hat / centos-stream / rpms / pcs on branch 9.4-pre3 : pcs-0.11.6-6

Miroslav Lisik added a comment - 2023/10/03 10:36 AM Upstream commit: https://github.com/ClusterLabs/pcs/commit/fd1484e229e63981fef19b3534bb119503c5c5a9 Updated commands: pcs resource create Test Environment: an arbitrary running cluster Test: # pcs resource create d-01 ocf:pacemaker:Dummy op monitor interval= Error: '' is not a valid interval value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue # pcs resource create d-01 ocf:pacemaker:Dummy op monitor timeout= Error: '' is not a valid timeout value, use time interval (e.g. 1, 2s, 3m, 4h, ...) Error: Errors have occurred, therefore pcs is unable to continue

pm-rhel added a comment - 2023/09/22 8:04 PM Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.