-
Story
-
Resolution: Done-Errata
-
Minor
-
rhel-9.0.0
-
pcs-0.11.6-6.el9
-
Low
-
FutureFeature
-
rhel-sst-high-availability
-
ssg_filesystems_storage_and_HA
-
13
-
19
-
3
-
QE ack
-
False
-
-
Yes
-
None
-
Pass
-
RegressionOnly
-
Enhancement
-
-
Done
-
-
All
-
None
+++ This bug was initially created as a clone of Bug #1807636 +++
Description of problem: Expected starting in Pacemaker 2.0.4 / RHEL 8.3, Pacemaker cluster properties marked as having the "time" type (cluster-recheck-interval, etc.) will accept ISO 8601 duration specifications in addition to the current possibilities (bare number of seconds or number plus units).
Steps to Reproduce:
1. pcs property set cluster-recheck-interval=P600S
Actual results:
Error: invalid value of property: 'cluster-recheck-interval=P600S', (use --force to override)
Expected results: pcs accepts a valid ISO 8601 interval
Additional notes: This was just an easy enhancement and not something driven by user demand, so it is very low priority.
— Additional comment from Ken Gaillot on 2020-02-26 20:45:23 CET —
FYI, pacemaker currently accepts a number, optionally with whitespace before or after, plus optional units:
ms or msec
us or usec
s or sec (or no unit specified)
m or min
h or hr
Anything else (including no number, unrecognized units, or anything after the units) is rejected.
- external trackers
- links to
-
RHBA-2023:124598 pcs bug fix and enhancement update
- mentioned on