Bug 1520798
| Summary: | pcs node standby --wait=... never terminates when using bundles [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | pkomarov |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | abeekhof, aherr, augol, cfeist, chjones, cluster-maint, dciabrin, kgaillot, lbezdick, mcornea, michele, mjuricek, mkrcmari, ushkalim, yprokule |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | 7.4 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1.1.16-12.el7_4.8 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the --wait option of the pcs utility sometimes blocked pcs commands indefinitely if clone notifications were not immediately runnable. This happened because Pacemaker unnecessarily waited until clone notifications had been completed when waiting for the cluster to stabilize. With this update, Pacemaker now ignores clone notification actions when waiting for cluster stability. As a result, pending clone notifications no longer block pcs commands when the cluster is stable.
|
Story Points: | --- |
| Clone Of: | 1519812 | Environment: | |
| Last Closed: | 2018-03-06 21:44:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1519812 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-12-05 07:50:17 UTC
Verified , # cat /etc/rhosp-release Red Hat OpenStack Platform release 12.0 (Pike) pcs status Cluster name: tripleo_cluster Stack: corosync Current DC: controller-2 (version 1.1.16-12.el7_4.8-94ff4df) - partition with quorum # time pcs node standby --wait=900 real 0m0.588s user 0m0.412s sys 0m0.120s [root@controller-0 ~]# echo $? 0 The bug was seen before the update to pacemaker-1.1.16-12.el7_4.8 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0409 |