Bug 1537557
| Summary: | OVN DB Pacemaker bundle : Pacemaker is either promoting a service on a wrong node or not promoting at all when the master node is stopped [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: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | abeekhof, aherr, cfeist, chjones, cluster-maint, dalvarez, kgaillot, lmiksik, mjuricek, mnovacek, nusiddiq, ushkalim |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | 7.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 1.1.16-12.el7_4.8 | Doc Type: | Bug Fix |
| Doc Text: |
When placing a resource that was colocated with a particular role of a bundle, Pacemaker did not correctly consider the role. As a consequence, these resources could be started or promoted on a node where the bundle did not have that role. With this update, Pacemaker now properly considers the role of the bundle when placing colocated resources, and the described problem no longer occurs.
|
Story Points: | --- |
| Clone Of: | 1527072 | 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: | 1527072 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-01-23 13:52:28 UTC
Verified ,
Colocation is implemented correct after ovndb_servers-master switch :
#Check colocation:
$ ansible controller-0 -m shell -b -a 'pcs config |grep "Colocation Constraints\|with ovndb_servers-master"'
controller-0 | SUCCESS | rc=0 >>
Colocation Constraints:
ip-172.17.0.18 with ovndb_servers-master (score:INFINITY) (rsc-role:Started) (with-rsc-role:Master)
#Before the failover :
$ ansible controller-0 -m shell -b -a 'pcs status'
controller-0 | SUCCESS | rc=0 >>
Cluster name: tripleo_cluster
Stack: corosync
Current DC: controller-1 (version 1.1.16-12.el7_4.8-94ff4df) - partition with
...
ip-172.17.0.18 (ocf::heartbeat:IPaddr2): Started controller-2
...
Master/Slave Set: ovndb_servers-master [ovndb_servers]
Masters: [ controller-2 ]
Slaves: [ controller-0 controller-1 ]
#After failover :
$ ansible controller-0 -m shell -b -a 'pcs status'
controller-0 | SUCCESS | rc=0 >>
Cluster name: tripleo_cluster
Stack: corosync
Current DC: controller-1 (version 1.1.16-12.el7_4.8-94ff4df)
...
ip-172.17.0.18 (ocf::heartbeat:IPaddr2): Started controller-1
...
Master/Slave Set: ovndb_servers-master [ovndb_servers]
Masters: [ controller-1 ]
Slaves: [ controller-0 ]
Stopped: [ controller-2 ]
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 |