No crash recovery / Can't run version upgrade stages manually
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-release-upgrader (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Hi,
I just tried to upgrade a machine (not the one I am writing this bug report on, so the attached data collection is useless) from 12.04 to 14.04.
The machine crashed while configuring new packages. (I'm not sure about the reason, but this machine has a problem that might be caused by the 12.04 kernel, which causes the machine to hang occasionally, that's why I wanted to upgrade to 14.04 and thus a newer kernel.)
After rebooting the machine it was in a stage just in the middle of the upgrade process. Although I could fix several things with a simple dpkg --configure --pending, I was not able to complete the upgrade process (e.g. cleanup).
There should be a way to manually recover from a crash and proceed with the update stage by stage, i.e. to complete what still needs to be done.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 3.13.0-15-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Thu Mar 6 09:44:51 2014
InstallationDate: Installed on 2013-04-29 (310 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
PackageArchitec
SourcePackage: ubuntu-
Symptom: ubuntu-
UpgradeStatus: Upgraded to trusty on 2014-03-05 (0 days ago)
VarLogDistupgra
| Hadmut Danisch (hadmut) wrote | #1 |
| Changed in ubuntu-release-upgrader (Ubuntu): | |
| importance: | Undecided → Wishlist |
| Changed in ubuntu-release-upgrader (Ubuntu): | |
| status: | New → Triaged |
| Brian Murray (brian-murray) wrote | #2 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 996916, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.