holland-xtrabackup dry run does not check for innobackup parse error

Bug #962441 reported by MikeG
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
holland-backup
Fix Released
Low
Unassigned

Bug Description

Currently if you have innodb=force in my.cnf, xtrabackup will fail:

https://bugs.launchpad.net/bugs/528752

If you have this option in my.cnf, a dry run will indicate a backup should succeed and it will later fail with xtrabackup: ambiguous option '--innodb=force'

During --dry-run, we should run if xtrabackup --help --verbose or some similar quick check that there are no errors

Revision history for this message
Andrew Garner (muzazzi) wrote :

This is probably a good idea. We should do the same with other plugins that run commands too (like mysqldump) that have some sort of "safe mode" to catch any obvious errors in execution.

Changed in holland-backup:
importance: Undecided → Low
milestone: none → 1.1.0a3
Revision history for this message
Andrew Garner (muzazzi) wrote :

holland-xtrabackup runs xtrabackup with --defaults-file=${holland-defaults} --help to verify the defaults file will be usable by xtrabackup. Further, xtrabackup upstream has finally merged a fix for --innobackup=force in recent versions.

Changed in holland-backup:
milestone: 1.1.0a3 → 1.0.8
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.