Bug 1481139
| Summary: | Ordering constraints involving bundles don't work [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: | Marian Krcmarik <mkrcmari> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.4 | CC: | abeekhof, aherr, cfeist, cluster-maint, kgaillot, michele, mjuricek, mnovacek, nbarcet, rscarazz, ushkalim |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | 7.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-1.1.16-12.el7_4.1 | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this update, Pacemaker did not correctly implement ordering constraints involving resources of the new "bundle" type. As a consequence, ordering constraints which included one or more "bundle" resources had no effect. With this update, the implementation has been improved, and the described problem no longer occurs. Note that the "bundle" type is a technology preview feature.
|
Story Points: | --- |
| Clone Of: | 1465519 | Environment: | |
| Last Closed: | 2017-09-05 11:31:54 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: | 1465519 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-08-14 08:24:35 UTC
Testing procedure (from parent bug): 1. Configure a cluster including a bundle resource and some other resource. 2. Configure an ordering constraint between the bundle resource and the other resource. Before the change, the ordering constraint will not work. After the change, it will. Feel free to repeat with various types of resources (primitives, groups, other bundles) as the other resource. Verified On: pacemaker-remote-1.1.16-12.el7_4.1.x86_64 Started the cluster and noticed via crm_mon that the ip resource start before the haproxy: Ordering Constraints: start ip-192.168.24.7 then start haproxy-bundle (kind:Optional) start ip-10.0.0.107 then start haproxy-bundle (kind:Optional) start ip-172.17.1.11 then start haproxy-bundle (kind:Optional) start ip-172.17.1.19 then start haproxy-bundle (kind:Optional) start ip-172.17.3.18 then start haproxy-bundle (kind:Optional) start ip-172.17.4.10 then start haproxy-bundle (kind:Optional) 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-2017:2587 |