Bug 1318744
| Summary: | HA | Galera fails to start after rebooting one of the controllers. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | resource-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | CC: | abeekhof, agk, cluster-maint, dciabrin, dmaley, fdinitto, jherrman, jschluet, kgaillot, lnatapov, mbayer, mburns, mcornea, mschuppe, oblaut, pablo.iranzo, paldeala, rcernin, royoung, scorcora, sknauss, ushkalim, yeylon |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | resource-agents-3.9.5-54.el7_2.9 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if a Galera node was unexpectedly terminated while a replication process was in progress, the MariaDB database could not be restarted on the node afterwards. With this update, the resource agent passes proper recovery arguments to MariaDB, which ensures that in the described circumstances, MariaDB can restart and synchronize to the Galera cluster as expected.
|
Story Points: | --- |
| Clone Of: | 1284526 | Environment: | |
| Last Closed: | 2016-04-14 21:55:52 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: | 1284526 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-03-17 16:15:26 UTC
tested on ospd8 according to instructions in BZ1284526 was unable to reproduce. 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://rhn.redhat.com/errata/RHBA-2016-0633.html |