Bug 1105607 - clustercheck script should read variables from /etc/sysconfig/clustercheck
Summary: clustercheck script should read variables from /etc/sysconfig/clustercheck
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: mariadb-galera
Version: 5.0 (RHEL 6)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 5.0 (RHEL 6)
Assignee: Ryan O'Hara
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks: 1122686
TreeView+ depends on / blocked
 
Reported: 2014-06-06 13:58 UTC by Ryan O'Hara
Modified: 2014-09-08 05:20 UTC (History)
2 users (show)

Fixed In Version: mariadb-galera-5.5.37-5.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1122686 (view as bug list)
Environment:
Last Closed: 2014-07-23 19:57:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan O'Hara 2014-06-06 13:58:40 UTC
The 'clustercheck' helper script should read all variables from /etc/sysconfig/clustercheck. This file contains information required to check mariadb-galera cluster state, such as username, password, port, etc. If clustercheck cannot read variables from /etc/sysconfig/culstercheck, it will use default values which will almost certainly fail.

Running clustercheck on RHOS-5.0, RHEL-6.5 currently gives:

# clustercheck
HTTP/1.1 503 Service Unavailable
Content-Type: text/plain
Connection: close
Content-Length: 44

Percona XtraDB Cluster Node is not synced.

In this particular case this is wrong. The node is an synced member of the mariadb-galera cluster. The expected result is:

# clustercheck 
HTTP/1.1 200 OK
Content-Type: text/plain
Connection: close
Content-Length: 40

Percona XtraDB Cluster Node is synced.

Using 'bash -x' to run clustercheck makes the undelying mysql command visible, and clearly shows that the default values are being used, not the values in /etc/sysconfig/cluster.

Comment 1 Ryan O'Hara 2014-06-06 14:03:10 UTC
I actually fixed this upstream a while back:

https://github.com/rohara/percona-clustercheck/commit/d0f366eeb91b72aaf022342b886062366a4e5f63

But it never got pulled into a RHOS-5.0 build. Easy fix, just requires rebuild.

Comment 2 Ryan O'Hara 2014-06-06 21:52:29 UTC
The clustercheck script in rhos-5.0-rhel-7 branch is already up to date. This bug only exists in rhos-5.0-rhel-6 branch.

Comment 4 Ami Jeain 2014-07-17 14:49:37 UTC
part of an HA setup


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