handle off-line database during upgrade more gracefully

Bug #440430 reported by Micah Gersten
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbconfig-common (Debian)
Fix Released
Unknown
dbconfig-common (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: request-tracker3.8

During the karmic beta upgrade from Jaunty, mysql was offline and it tried to upgrade the database for RT.

ProblemType: Package
Architecture: amd64
Date: Fri Oct 2 02:36:31 2009
DistroRelease: Ubuntu 9.10
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 1
Package: request-tracker3.8 3.8.4-1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
SourcePackage: request-tracker3.8
Title: package request-tracker3.8 3.8.4-1 failed to install/upgrade:
Uname: Linux 2.6.30-10-generic x86_64

Revision history for this message
Micah Gersten (micahg) wrote :
Revision history for this message
Dominic Hargreaves (dom) wrote :

Does running "dpkg-reconfigure request-tracker3.8" manually do the upgrade for you?

Since the database upgrades are handled by dbconfig-common, I will move this bug there; but I'm not sure that there is a real solution to this except perhaps to provide more hints in the error.

affects: request-tracker3.8 (Ubuntu) → dbconfig-common (Ubuntu)
Revision history for this message
Chuck Short (zulcss) wrote :

If the database is offline then dbconfig-common will error out. This should be changed to handle things more gracefully.

Regards
chuck

Changed in dbconfig-common (Ubuntu):
status: New → Confirmed
Chuck Short (zulcss)
Changed in dbconfig-common (Ubuntu):
status: Confirmed → Triaged
tags: added: dist-upgrade
summary: - package request-tracker3.8 3.8.4-1 failed to install/upgrade:
+ handle off-line database during upgrade more gracefully
Changed in dbconfig-common (Debian):
status: Unknown → New
Changed in dbconfig-common (Debian):
status: New → Fix Released
Revision history for this message
Paul Gevers (paul-climbing) wrote :

This was fixed in 1.8.50 which is part of The Wily Werewolf. So closing this bug.

Changed in dbconfig-common (Ubuntu):
status: Triaged → 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.