Bug 1465519
| Summary: | Ordering constraints involving bundles don't work | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ken Gaillot <kgaillot> | |
| Component: | pacemaker | Assignee: | Andrew Beekhof <abeekhof> | |
| Status: | CLOSED ERRATA | QA Contact: | pkomarov | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.4 | CC: | abeekhof, aherr, cfeist, cluster-maint, kgaillot, michele, mnovacek, nbarcet, ushkalim | |
| Target Milestone: | rc | Keywords: | Triaged, ZStream | |
| Target Release: | 7.5 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | pacemaker-1.1.18-1.el7 | Doc Type: | No Doc Update | |
| Doc Text: |
(Bundles were tech preview in 7.4, so bug fixes do not need to be documented in 7.5.)
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: | ||||
| : | 1481139 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-10 15:30:29 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: | 1481139 | |||
|
Description
Ken Gaillot
2017-06-27 14:40:57 UTC
Fixed upstream Testing procedure: 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 , tested constraints : Ordering Constraints: start ip-192.168.24.9 then start haproxy-bundle (kind:Optional) results : crm_mon indicates correct order during cluster startup results from the logs ;the order is preserved : [614489] <lrm_rsc_op id="ip-192.168.24.9_last_0" operation_key="ip-192.168.24.9_start_0" operation="start" ... ... [614489] <lrm_rsc_op id="haproxy-bundle-docker-2_last_0" operation_key="haproxy-bundle-docker-2_start_0" operation="start" 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 |