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 1620081 - Allow for explicit "sequence points" in pcs based scripting, e.g. by the means of "pcs cluster settle cib"
Summary: Allow for explicit "sequence points" in pcs based scripting, e.g. by the mean...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.7
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-22 12:29 UTC by Jan Pokorný [poki]
Modified: 2024-02-16 16:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-02-16 16:29:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1459251 0 medium CLOSED pcs should not guess expected status of a resource when --wait is used 2024-01-09 10:08:01 UTC
Red Hat Bugzilla 1619265 0 low CLOSED As a single entrypoint towards pacemaker, pcs should smartly coalesce all "--wait" synchronous hooking 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker   RHEL-25854 0 None Migrated None 2024-02-16 16:29:36 UTC
Red Hat Issue Tracker RHELPLAN-169487 0 None None None 2024-02-16 16:29:07 UTC

Internal Links: 1459251 1619265

Description Jan Pokorný [poki] 2018-08-22 12:29:19 UTC 
Intended use spurred with [bug 1619265] is:

> perform bunch of changes to cluster state/configuration, only then
> arrange for waiting until it all sinks in and the cluster at pacemaker
> level finally "settles"

Implementation-wise:

> crm_resource --wait [--timeout=TIMEOUT]

Notes:

- modelled according to "udevadm settle" (and perhaps others)
  administrators can be familiar with

- why not just "pcs cluster settle"?  there are more in-flight,
  transients states that one may also want to establish "sequential
  points" for, e.g. "pcs cluster start"; "pcs cluster settle" could
  then easily be dedicated to mean as a catch-all (or smart decision
  to be made automatically) later on
Comment 3 RHEL Program Management 2021-02-15 07:41:50 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 6 RHEL Program Management 2024-02-16 16:29:09 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 7 RHEL Program Management 2024-02-16 16:29:41 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.