bacula-sqlite3 scripts contains XXX instead of real DB name

Bug #1426312 reported by K
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Won't Fix
Medium
Unassigned

Bug Description

The file /etc/bacula/scripts/delete_catalog_backup contains :
#!/bin/sh
#
# This script deletes a catalog dump
#
db_name=XXX_DBNAME_XXX

rm -f /var/lib/bacula/${db_name}.sql

It should contain :
#!/bin/sh
#
# This script deletes a catalog dump
#
db_name=bacula

rm -f /var/lib/bacula/${db_name}.sql

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bacula-director-sqlite3 5.2.5-0ubuntu6.2
ProcVersionSignature: Ubuntu 3.13.0-46.75~precise1-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Fri Feb 27 11:47:27 2015
InstallationMedia: EOLE 2.4.1-rc1 "Precise Pangolin" - Release amd64 (20141205.1)
MarkForUpload: True
SourcePackage: bacula
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
K (c-walou) wrote :
Revision history for this message
Nish Aravamudan (nacc) wrote :

This is not the case on 16.04, which version of Ubuntu are you on?

Changed in bacula (Ubuntu):
status: New → Fix Released
Revision history for this message
K (c-walou) wrote :

root@machine:~# cat /etc/bacula/scripts/delete_catalog_backup
#!/bin/sh
#
# This script deletes a catalog dump
#
db_name=XXX_DBNAME_XXX

rm -f /var/lib/bacula/${db_name}.sql

root@machine:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.5 LTS"

Changed in bacula (Ubuntu):
status: Fix Released → New
Revision history for this message
Robie Basak (racb) wrote :

Thanks. Let's set this to Fix Released to represent the current development release, and I'll create a task to track the status of the problem on 12.04 (Precise).

Changed in bacula (Ubuntu):
status: New → Fix Released
Revision history for this message
Robie Basak (racb) wrote :

Presumably the workaround for this is trivial - fix /etc/bacula/scripts/delete_catalog_backup as you've described? Setting Importance to Medium accordingly.

Changed in bacula (Ubuntu Precise):
importance: Undecided → Medium
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in bacula (Ubuntu Precise):
status: New → Won't Fix
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.