Handle empty passwords in wsrep_sst scripts

Bug #1183530 reported by Raghavendra D Prabhu on 2013-05-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released
Raghavendra D Prabhu

Bug Description

As the title says, handle it.

Related branches

        if [ "${AUTH[0]}" != "(null)" ]; then

        if [ ${#AUTH[*]} -eq 2 ]; then
           INNOBACKUPEX_ARGS="${INNOBACKUPEX_ARGS} --password=${AUTH[1]}"


I think the above can be removed. If there is any user/pass required it should be passed through my.cnf.

It should be removable for mysqldump too IMO. mysqldump doesn't even take empty password. Also, if required it can be passed through [mysqldump] in my.cnf.

If both those aren't required, what is the point of wsrep_sst_auth?

Some people may want to use a different user for innobackupex in
root:root 600 file which is !included. So, credentials for the
SST user can be put there.

So, I guess the settings can stay.

Changed in percona-xtradb-cluster:
assignee: nobody → Raghavendra D Prabhu (raghavendra-prabhu)
status: New → Fix Committed
milestone: none → 5.5.31-24.8
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released
Changed in codership-mysql:
milestone: none → 5.5.31-23.7.5
Changed in codership-mysql:
status: New → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1357

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers