-
Story
-
Resolution: Done-Errata
-
Normal
-
rhel-9.0.0
-
pcs-0.11.7-3.el9
-
FutureFeature
-
rhel-sst-high-availability
-
ssg_filesystems_storage_and_HA
-
13
-
19
-
3
-
False
-
-
Yes
-
None
-
Pass
-
Automated
-
Feature
-
-
Done
-
-
Unspecified
-
None
Intended use spurred with bz1619265 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:
- modeled 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
- is related to
-
RHEL-21051 [RFE] pcs should not guess expected status of a resource when --wait is used [rhel-9]
- Closed
- external trackers
- links to
-
RHBA-2024:133004 pcs bug fix and enhancement update
- mentioned on
(1 links to, 1 mentioned on)