Bug 1807636

Summary:	Support ISO 8601 duration specifications for pacemaker "time" properties
Product:	Red Hat Enterprise Linux 8	Reporter:	Ken Gaillot <kgaillot>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED WONTFIX	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	low
Version:	8.2	CC:	cfeist, cluster-maint, idevat, mlisik, mmazoure, mpospisi, omular, tojeline
Target Milestone:	rc	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	2112268 (view as bug list)		Environment:
Last Closed:	2023-01-12 07:27:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ken Gaillot 2020-02-26 19:38:28 UTC

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.

Comment 1 Ken Gaillot 2020-02-26 19:45:23 UTC

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.

Comment 4 RHEL Program Management 2021-08-26 07:27:10 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 9 RHEL Program Management 2023-01-12 07:27:48 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.