Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1376908 - mysqld service prevents haproxy to get started and deployment fails
mysqld service prevents haproxy to get started and deployment fails
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: mariadb-galera (Show other bugs)
5.0 (RHEL 7)
Unspecified Unspecified
urgent Severity urgent
: beta
: 5.0 (RHEL 7)
Assigned To: Michael Bayer
Shai Revivo
: ZStream
Depends On: 1375184
Blocks:
  Show dependency treegraph
 
Reported: 2016-09-16 15:30 EDT by Michael Bayer
Modified: 2016-10-13 10:14 EDT (History)
16 users (show)

See Also:
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.
Story Points: ---
Clone Of: 1375184
Environment:
Last Closed: 2016-10-13 10:14:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2059 normal SHIPPED_LIVE Important: mariadb-galera security and bug fix update 2016-10-13 14:13:54 EDT

  None (edit)
Comment 7 errata-xmlrpc 2016-10-13 10:14:31 EDT
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.