[SRU] Database not upgraded while upgrading bacula

Since the script "update_bacula_tables" is missing from the install, normaly installed at /etc/bacula/scripts --- this is a showbreaker.
The script isn't found in the documentation as well.

Hi Thomas

The upgrade script for 12->14 for postgresql can be found in /usr/share/bacula-director.

Does your installation use dbconfig? I believe that this should automatically upgrade the database but if you are not using dbconfig you will need to run this script manually.

Thnaks

dbconfig is used. But the update not applied. The script in /usr/share/bacula-director differs from the one given in the bacula sources (where I found it). The differences are minor and shouldn't matter, but it is a pitty to find scripts referenced to be found at /etc/bacula/scripts in the manual at /usr/share/bacula-director. This means the manuals would have to be updated too, but this wasn't done.

Looks like the dbconfig upgrade steps are missing for the version in precise.

Raising tasks - will target SRU for 12.04.1 (but probably earlier).

Had to work around a misconfiguration in the director config for mysql on a fresh install but confirmed:

Please correct configuration file: /etc/bacula/bacula-dir.conf
14-Jun 12:58 bacula-dir JobId 0: Fatal error: Version error for database "bacula". Wanted 14, got 12
14-Jun 12:58 bacula-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bacula".
14-Jun 12:58 bacula-dir JobId 0: Fatal error: Version error for database "bacula". Wanted 14, got 12
14-Jun 12:58 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf

This bug was fixed in the package bacula - 5.2.5-0ubuntu7

---------------
bacula (5.2.5-0ubuntu7) quantal; urgency=low

  * Ensure bacula database is upgraded from 12->14 as part of
    upgrade to 5.2.x (LP: #980189):
    - d/rules: Add dbconfig-common upgrade step for 5.2.5-0ubuntu6.1 for
      all database types.
 -- James Page <email address hidden> Thu, 14 Jun 2012 16:09:41 +0100

Uploaded to precise-proposed for SRU team review.

Hello Thomas, or anyone else affected,

Accepted bacula into precise-proposed. The package will build now and be available in a few hours. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Verified as fixed via aptitude upgrade. I didn't have to do anything manually, can read previous and generate new backups so far.

This bug was fixed in the package bacula - 5.2.5-0ubuntu6.1

---------------
bacula (5.2.5-0ubuntu6.1) precise-proposed; urgency=low

  * Ensure bacula database is upgraded from 12->14 as part of
    upgrade to 5.2.x (LP: #980189):
    - d/rules: Add dbconfig-common upgrade step for 5.2.5-0ubuntu6.1 for
      all database types.
 -- James Page <email address hidden> Thu, 14 Jun 2012 15:52:27 +0100

Is this bug really fixed in precise? I just upgraded from oneiric using 'do-release-upgrade' and director is not starting:

28-Jul 19:20 bacula-dir JobId 0: Fatal error: Version error for database "bacula". Wanted 14, got 12
28-Jul 19:20 bacula-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bacula".
28-Jul 19:20 bacula-dir JobId 0: Fatal error: Version error for database "bacula". Wanted 14, got 12
28-Jul 19:20 bacula-dir ERROR TERMINATION

Database is MySQL.

The packages in the proposed worked for me at least like a treat:

Upgrade: bacula-sd-mysql:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-client:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-director-mysql:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-common:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-console:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-fd:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-sd:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-server:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-common-mysql:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-director-common:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1), bacula-console-qt:amd64 (5.2.5-0ubuntu6, 5.2.5-0ubuntu6.1)
End-Date: 2012-06-19 12:27:20

and my director started fine after that.

Sorry, I did not notice that the package is not yet in precise-updates. I did not enable precise-proposed.

Hi Fabian,
I thought they were released by the maintainer to the wild. Apt-cache shows the 5.2.5-0ubuntu6.1 for the bacula-server version.

James Page's log shows (http://bazaar.launchpad.net/~james-page/ubuntu/precise/bacula/fix-db-upgrade/revision/87#debian/rules) that it is missing the upgrade script which looks like it is not running the following:
/usr/share/dbconfig-common/data/bacula-director-mysql/upgrade/mysql/5.2.5-0ubuntu6.1

If you can check the file exists, you should be able to run it by hand as a worst-case fallback.