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.

Description of problem:
In RDO upstream, we deploy OpenStack clouds with mariadb 10.1.x.

Since MariaDB 10.1.21 [1], mysqld_safe relies on a helper subprocess to write into log files. This new logging mechanism expects log file to be writable by the user configured to run mysqld.

When the galera resource agent attempts to bootstrap the galera cluster, it requests mysqld_safe to output replication information into a temporary file   
 own by root. This does not work anymore because mysql doesn't have rights to write to that file.

[1] https://github.com/MariaDB/server/commit/8fcdd6b0ecbb966f4479856efe93a963a7a422f7


Version-Release number of selected component (if applicable):
resource-agents-3.9.5-105.el7_4.3.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install mariadb 10.1.30 from RDO
2. Create a galera resource in pacemaker

Actual results:
mysql servers can't be started because the resource agent doesn't get the replication information out of mysqld_safe.

Expected results:
mysql servers to be started

Additional info:

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-2018:0757