Bug 1620081

Summary:	Allow for explicit "sequence points" in pcs based scripting, e.g. by the means of "pcs cluster settle cib"
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Pokorný [poki] <jpokorny>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.7	CC:	cfeist, cluster-maint, idevat, omular, tojeline
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-02-16 16:29:41 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 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.