Bug 1376910

Summary: mysqld service prevents haproxy to get started and deployment fails
Product: Red Hat OpenStack Reporter: Michael Bayer <mbayer>
Component: mariadb-galeraAssignee: Michael Bayer <mbayer>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.0 (Kilo)CC: bperkins, dbecker, dciabrin, jschluet, mbayer, mburns, mcornea, morazi, nlevinki, rhel-osp-director-maint, royoung, sasha, slong, srevivo, ushkalim
Target Milestone: betaKeywords: ZStream
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mariadb-galera-5.5.42-4.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 14:04:47 UTC Type: Bug
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: 1375184    
Bug Blocks:    

Comment 2 nlevinki 2016-10-05 10:35:34 UTC
Automation passed
https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS7/job/qe-7_director-rhel-7.2-virthost-1cont_1comp_1ceph-ipv4-vxlan-ceph-ssl/3/
using this rpm
mariadb-galera-server-5.5.42-5.el7ost.x86_64

Comment 4 errata-xmlrpc 2016-10-13 14:04:47 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-2061.html