[Bug 876146] Re: Upgrading Ubuntu is risky (unusable or unbootable PC). What can be done to safeguard data, revert failed upgrades and overall reduce the risks?
Matthias Kretz
kretz at kde.org
Mon Jan 30 21:23:03 UTC 2012
Hi, question: How does the upgrade QA work? Does it rely solely on users
that do the upgrade at Alpha and Beta stages? Do you have a simple way
to repeat upgrade processes to test the progress of stabilization?
Actually I'd be happy to do upgrade tests (especially since my experience is that something always breaks). This scenario could work for me:
* Alpha/Beta is announced
* When I know I won't need my computer for the next few hours I will tell it to do a test upgrade
* The upgrade process creates a bootable USB key or CD to restore the system later
* First it tests whether this restore system boots, only if this works does the upgrade proceed
* After the upgrade is done I can check for problems and report them (this must be automated as much as possible)
* When done, I reboot into the restore CD/USB and get my old system back
* If I get notified that some of my issues should be fixed I can repeat the process to verify
Except for bootloader issues this should be easily possible given enough
space on the harddrive...
PS: I installed Ubuntu for a friend and when the popup appeared that a
distribution upgrade is available, the first thing I did was call my
friend and tell him to not click that button - I was just in time to
stop him (and I'm happy I did - two out of two Oneiric upgrades broke
for me. I couldn't reserve enough time yet for the remaining computers
that want to upgrade.).
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/876146
Title:
Upgrading Ubuntu is risky (unusable or unbootable PC). What can be
done to safeguard data, revert failed upgrades and overall reduce the
risks?
Status in NULL Project:
Invalid
Status in “update-manager” package in Ubuntu:
Confirmed
Bug description:
Please note: This bug report will now be used to track specific code
changes for reducing the risk of upgrading (see comment #14). Please
stay on topic. We also have enough cases of problematic upgrades.
Thank You.
*Report:
===References:
- Typical bad upgrade user case (forum post):
http://ubuntuforums.org/showthread.php?t=1860359
- Unusable upgrade pic (unbootable)
http://ubuntuforums.org/attachment.php?attachmentid=204320&d=1318627364
- [ubuntu] Thread for failed upgrades (huge list within 24 to 48 hours)
http://ubuntuforums.org/showthread.php?t=1858475
- Unofficial poll, but might serve useful as another source of data and user cases. Also, reference for future polls. Current sample of about 3k users, ~22% needed to reinstall.
http://www.omgubuntu.co.uk/2011/10/how-well-did-your-ubuntu-11-10-upgrade-go/
http://www.reddit.com/r/Ubuntu/comments/lm036/how_well_did_your_ubuntu_1110_upgrade_go/
===Description:
Lots of angry users with broken computers that need rescue...
The friendly Upgrade popup has become a mouse trap for new and
unsuspecting users.
Warnings and fail-safe alternatives and/or advise should be offered.
Specially for users who cant risk having their computers broken (only
have 1 OS). Nor have the knowledge, will, time and patience to fix
something like this.
I think this should be Critical for "Precise" pangolin as the number
of users upgrading will be in the Tens if not hundreds of thousands
(or millions...), since this will be the new LTS.
===Initial proposal:
See comment #10:
https://bugs.launchpad.net/ayatana-design/+bug/876146/comments/10
===Other related helpers for the upgrade problem:
-There is no "feedback and reporting tool to count the number of bad
upgrades" and their related causes. Users should be able to give
immediate feedback after every upgrade (successful or not). "Ubuntu-
bug upgrade-report" on startup after an upgrade and a section on
launchpad or dedicated site.
-Update/upgrade manager should offer an auto-backup wizard to safe
guard important user files to another partition, external storage or
online (See comment #10).
-Also separate branches for testing and a better release process/cycle would certainly help diminish the amount of bugs and many upgrade problems as it has been discussed here:
http://netsplit.com/2011/09/08/new-ubuntu-release-process/
To manage notifications about this bug go to:
https://bugs.launchpad.net/null/+bug/876146/+subscriptions
More information about the foundations-bugs
mailing list