RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1391470 - Galera resource agent cannot recover WSREP last commit with recent mariadb version
Summary: Galera resource agent cannot recover WSREP last commit with recent mariadb ve...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.3
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: 7.4
Assignee: Damien Ciabrini
QA Contact: Asaf Hirshberg
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 11:55 UTC by Damien Ciabrini
Modified: 2017-08-01 14:55 UTC (History)
10 users (show)

Fixed In Version: resource-agents-3.9.5-84.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 14:55:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1844 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2017-08-01 17:49:20 UTC

Description Damien Ciabrini 2016-11-03 11:55:49 UTC 
Description of problem:

Starting with mariadb 10.1.18, mysqld_safe does no longer output the WSREP last commit to the standard output when called with command line option --wsrep-recover. Instead, it logs that information into mariadb's error log.

Because of this change, the galera resource agent can no longer recover the information and cannot determine the node to bootstrap the galera cluster from.

RDO Openstack uses the galera resource agent from CentOS, which is sync'd from RHEL, but they recently switched to mariadb 10.1.18, which prevents the galera cluster from starting.  

How reproducible:
Always starting with mariadb 10.1.18

Steps to Reproduce:
1. create a galera resource in pacemaker
2. enable the resource

Actual results:
the galera cluster won't come up, resource stuck in slave

Expected results:
the cluster should come up

Additional info:
Comment 1 Michele Baldessari 2016-11-03 13:08:10 UTC 
For the time being in upstream we will back out the commit that changed this behaviour in "mysqld_safe --wsrep-recover" via https://bugs.launchpad.net/tripleo/+bug/1638864

Once we land a fix in the RA we can remove the revert of the offending patch
Comment 3 Damien Ciabrini 2016-11-18 13:55:26 UTC 
Proposed fix in https://github.com/ClusterLabs/resource-agents/pull/884 has been merged in upstream.
Comment 7 Damien Ciabrini 2017-01-03 15:22:13 UTC 
Proposed high level steps for testing:
- Test with RDO to verify that fix works with mariadb 10:
  . Deploy a Newton stack with 3-node HA controllers 
  . Once done, stop galera service: "pcs resource disable galera"
  . install the test resource-agents package
  . downgrade mariadb* packages to 10.1.18-2 on all controllers, to reintroduce the breaking change in mariadb [1]
  . restart galera: "pcs resource enable galera"
  . ensure that all galera nodes have restarted with "pcs status"

- Test with RHEL to verify that fix doesn't introduce regression with mariadb 5.5
  . Deploy an OSP10 with 3-node HA controllers
  . Once done, stop galera service: "pcs resource disable galera"
  . install the test resource-agents package
  . restart galera: "pcs resource enable galera"
  . ensure that all galera nodes have restarted with "pcs status"
  

[1] see https://bugs.launchpad.net/tripleo/+bug/1638864
Comment 8 Raoul Scarazzini 2017-01-05 15:37:17 UTC 
(In reply to Damien Ciabrini from comment #7)
> Proposed high level steps for testing:
> - Test with RDO to verify that fix works with mariadb 10:
>   . Deploy a Newton stack with 3-node HA controllers 
>   . Once done, stop galera service: "pcs resource disable galera"
>   . install the test resource-agents package
>   . downgrade mariadb* packages to 10.1.18-2 on all controllers, to
> reintroduce the breaking change in mariadb [1]
>   . restart galera: "pcs resource enable galera"
>   . ensure that all galera nodes have restarted with "pcs status"

I made this validation test on the latest CentOS (7.3.1611), stopping galera, downgrading on all the controllers the galera packages (yum -y downgrade mariadb*-10.1.18-2.el7.x86_64) and then restarting with success the galera resource with pcs.

> - Test with RHEL to verify that fix doesn't introduce regression with
> mariadb 5.5
>   . Deploy an OSP10 with 3-node HA controllers
>   . Once done, stop galera service: "pcs resource disable galera"
>   . install the test resource-agents package
>   . restart galera: "pcs resource enable galera"
>   . ensure that all galera nodes have restarted with "pcs status"
>   
> 
> [1] see https://bugs.launchpad.net/tripleo/+bug/1638864
Comment 9 Asaf Hirshberg 2017-02-27 13:21:15 UTC 
Verified on osp-10 latest on rhel, using steps from comment #8
Comment 10 errata-xmlrpc 2017-08-01 14:55:11 UTC 
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:1844
Note You need to log in before you can comment on or make changes to this bug.