This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2112268 - [RFE] Support ISO 8601 duration specifications for pacemaker "time" properties
Summary: [RFE] Support ISO 8601 duration specifications for pacemaker "time" properties
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.0
Hardware: All
OS: All
low
low
Target Milestone: rc
: 9.4
Assignee: Miroslav Lisik
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-29 08:15 UTC by Tomas Jelinek
Modified: 2023-09-22 19:53 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Support ISO 8601 duration specifications for pacemaker "time" properties. Reason: Pacemaker supports ISO 8601 duration specification since Pacemaker 2.0.4 / RHEL 8.3. Result: Pcs allows to specify values for pacemaker "time" properties according to ISO 8601 duration specification.
Clone Of: 1807636
Environment:
Last Closed: 2023-09-22 19:53:46 UTC
Type: Story
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ClusterLabs pcs pull 712 0 None Merged Support ISO 8601 duration specifications for pacemaker "time" properties 2023-07-21 11:13:27 UTC
Red Hat Issue Tracker   RHEL-7672 0 None Migrated None 2023-09-22 19:51:08 UTC
Red Hat Issue Tracker RHELPLAN-129618 0 None None None 2022-07-29 08:31:05 UTC

Description Tomas Jelinek 2022-07-29 08:15:32 UTC
+++ 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.

Comment 3 Tomas Jelinek 2023-07-21 11:12:12 UTC
Upstream patch from community: https://github.com/ClusterLabs/pcs/commit/d22b63fd3ef9f7f4ce9a80044fa811f8b3bacf99

Comment 5 Miroslav Lisik 2023-07-24 07:40:05 UTC
Upstream commit: https://github.com/ClusterLabs/pcs/commit/d22b63fd3ef9f7f4ce9a80044fa811f8b3bacf99

Updated command:
pcs property set

All pacemaker time properties except stonith-watchdog-timeout supports values
defined in ISO 8601 duration format:
https://en.wikipedia.org/wiki/ISO_8601#Durations

Environment: A runnig cluster

Test:
# pcs property set cluster-delay=P60S
# pcs property config cluster-delay
Cluster Properties: cib-bootstrap-options
  cluster-delay=P60S

Comment 8 RHEL Program Management 2023-09-22 19:48:31 UTC
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.

Comment 9 RHEL Program Management 2023-09-22 19:53:46 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.