Bug 1376908 - mysqld service prevents haproxy to get started and deployment fails
Summary: mysqld service prevents haproxy to get started and deployment fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: mariadb-galera
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 5.0 (RHEL 7)
Assignee: Michael Bayer
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On: 1375184
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-16 19:30 UTC by Michael Bayer
Modified: 2023-02-22 23:02 UTC (History)
15 users (show)

Fixed In Version: mariadb-galera-5.5.42-1.1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Because Red Hat Enterprise Linux 7.3 changed the return format of the "systemctl is-enabled" command as consumed by shell scripts, the mariadb-galera RPM package, upon installation, erroneously detected that the MariaDB service was enabled when it was not. As a result, the Red Hat OpenStack Platform installer, which then tried to run mariadb-galera using Pacemaker and not systemd, failed to start Galera. With this update, mariadb-galera's RPM installation scripts now use a different systemctl command, correctly detecting the default MariaDB as disabled, and the installer can succeed.
Clone Of: 1375184
Environment:
Last Closed: 2016-10-13 14:14:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2059 0 normal SHIPPED_LIVE Important: mariadb-galera security and bug fix update 2016-10-13 18:13:54 UTC

Comment 7 errata-xmlrpc 2016-10-13 14:14:31 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://rhn.redhat.com/errata/RHSA-2016-2059.html


Note You need to log in before you can comment on or make changes to this bug.