Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1109306

Summary: mysql_install_db script should search correct paths
Product: Red Hat OpenStack Reporter: Ryan O'Hara <rohara>
Component: mariadb-galeraAssignee: Ryan O'Hara <rohara>
Status: CLOSED ERRATA QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 7)CC: yeylon
Target Milestone: rc   
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mariadb-galera-5.5.37-6.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1115619 1139382 (view as bug list) Environment:
Last Closed: 2014-07-08 15:15:29 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:    
Bug Blocks: 1115619, 1139382, 1139384, 1139386    
Attachments:
Description Flags
Fix paths in mysql_install_db script none

Description Ryan O'Hara 2014-06-13 15:40:18 UTC 
The mysql_install_db script will try to determine paths (eg. langdir, pkgdatadir) if "basedir" is set. This is done by searching for a particular file in a couple hard-coded subdirectories. The problem is that these subdirectories are hard-coded. For example, determining pkgdatadir is done by searching for the file "fill_help_tables.sql" in the "$basedir/share" and "$basedir/mysql". For mariadb-galera, this is wrong. This should be "$basedir/mariadb-galera".

This causes problem when mariadb-galera is deployed via pupet since it will set "basedir" in /etc/my.cnf before mysql_install_db is run. The quick fix here is to simply change the hard-coded paths.
Comment 1 Ryan O'Hara 2014-06-13 16:05:24 UTC 
Created attachment 908638 [details]
Fix paths in mysql_install_db script
Comment 7 errata-xmlrpc 2014-07-08 15:15:29 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.

http://rhn.redhat.com/errata/RHEA-2014-0845.html