Bug 1522822
| Summary: | Resources are not moved to different node once the node they were started on is reset ungracefully | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marian Krcmarik <mkrcmari> | |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> | |
| Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.4 | CC: | abeekhof, aherr, cfeist, chjones, cluster-maint, jruemker, mnovacek | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | 7.5 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | pacemaker-1.1.18-7 | Doc Type: | No Doc Update | |
| Doc Text: |
Previously, it was sometimes impossible to recover resources from container bundles elsewhere after the host node of the container failed. With this update, Pacemaker now handles ordering of nested Pacemaker Remote connections correctly. As a result, resource recovery proceeds normally for bundled resources.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1527810 (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: | 1527810 | |||
|
Description
Marian Krcmarik
2017-12-06 14:11:38 UTC
We need all except the "Test:" at the end. + b82a555: Test: PE: Ensure stop operations occur after stopped remote connections have been brought up (HEAD -> master, public/master, origin/master, origin/HEAD) + 7758ecb: Fix: PE: Ensure stop operations occur after stopped remote connections have been brought up + 1c6c22a: Fix: PE: Remote connection resources are safe to to require only quorum + 03041d7: Fix: PE: Only allowed nodes need to be considered when ordering resource startup after _all_ recovery + d96e871: Fix: PE: Ordering bundle child stops/demotes after container fencing causes graph loops + 33f50f6: Fix: PE: Passing boolean instead of a pointer 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 |