Bug 1519812
| Summary: | pcs node standby --wait=... never terminates when using bundles | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Michele Baldessari <michele> | |
| 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, mkrcmari, ushkalim, yprokule | |
| Target Milestone: | rc | Keywords: | Triaged, ZStream | |
| Target Release: | 7.5 | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | pacemaker-1.1.18-10.el7 | 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: | ||||
| : | 1520798 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-10 15:34:42 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1520798 | |||
|
Description
Michele Baldessari
2017-12-01 13:40:40 UTC
Setting needinfo on me as Ken needs confirmation that 7.5 is working ok in this regard Can you attach a pe-input (or pcs cluster report) from when it was blocked? It doesn't happen in my simple tests, so I suspect it's going to be specific to something in your configuration. As a potential additional info: the undstandby command works as expected [root@overcloud-controller-2 tmp]# pcs node unstandby overcloud-controller-1 --wait=900 [root@overcloud-controller-2 tmp]# echo $? 0 Assigning back to HA team for builds and z-streams Verified, # cat /etc/rhosp-release Red Hat OpenStack Platform release 12.0 (Pike) # pcs status |head -n 3 Cluster name: tripleo_cluster Stack: corosync Current DC: controller-1 (version 1.1.18-10.el7-2b07d5c5a9) - partition with quorum # time pcs node standby --wait=900 real 0m48.888s user 0m2.034s sys 0m0.138s [root@controller-0 ~]# echo $? 0 Verified,
# pcs status |head -n 3
Cluster name: tripleo_cluster
Stack: corosync
Current DC: controller-1 (version 1.1.18-10.el7-2b07d5c5a9) - partition with quorum
pcs config :
Colocation Constraints:
ip-172.17.0.11 with ovndb_servers-master (score:INFINITY) (rsc-role:Started) (with-rsc-role:Master)
Before ovndb_servers-master standby:
ip-172.17.0.11 (ocf::heartbeat:IPaddr2): Started controller-0
Master/Slave Set: ovndb_servers-master [ovndb_servers]
Masters: [ controller-0 ]
Slaves: [ controller-1 controller-2 ]
After ovndb_servers-master standby:
ip-172.17.0.11 (ocf::heartbeat:IPaddr2): Started controller-2
Master/Slave Set: ovndb_servers-master [ovndb_servers]
Masters: [ controller-2 ]
Slaves: [ controller-1 ]
Stopped: [ controller-0 ]
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/RHEA-2018:0860 |