release upgrade fails on some aptcdrom atribute error

Bug #1357005 reported by Daniel Simacek
52
This bug affects 9 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Release upgrade error to 14.04

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.14.17
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
Uname: Linux 3.2.0-67-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Thu Aug 14 10:46:19 2014
GsettingsChanges:
 com.ubuntu.update-manager first-run false
 com.ubuntu.update-manager launch-time 1408038304
 com.ubuntu.update-manager show-details true
 com.ubuntu.update-manager window-height 717
 com.ubuntu.update-manager window-width 512
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
Symptom: ubuntu-release-upgrader-core
UpgradeStatus: Upgraded to precise on 2014-08-14 (0 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Daniel Simacek (simacekd-c) wrote :
Revision history for this message
Daniel Simacek (simacekd-c) wrote :

Any indea why is this update failing on my system?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

What command line did you use to perform the upgrade? It looks like you were trying to upgrade via a CD-ROM or similar media. Thanks!

Revision history for this message
Brian Murray (brian-murray) wrote :

Traceback (most recent call last):

  File "/tmp/update-manager-e8K5WV/trusty", line 10, in <module>
    sys.exit(main())

  File "/tmp/update-manager-e8K5WV/DistUpgrade/DistUpgradeMain.py", line 243, in main
    if app.run():

  File "/tmp/update-manager-e8K5WV/DistUpgrade/DistUpgradeController.py", line 1827, in run
    return self.fullUpgrade()

  File "/tmp/update-manager-e8K5WV/DistUpgrade/DistUpgradeController.py", line 1781, in fullUpgrade
    self.abort()

  File "/tmp/update-manager-e8K5WV/DistUpgrade/DistUpgradeController.py", line 1337, in abort
    self.aptcdrom.restore_backup(self.sources_backup_ext)

AttributeError: 'AptCdrom' object has no attribute 'restore_backup'

Changed in update-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

All the sources.list files have commented out 'deb cdrom:' lines in them, e.g.

# deb cdrom:[Ubuntu 12.04.1 LTS _Precise Pangolin_ - Release amd64 (20120823.1)]/ dists/precise/main/binary-i386/
# deb cdrom:[Ubuntu 12.04.1 LTS _Precise Pangolin_ - Release amd64 (20120823.1)]/ dists/precise/restricted/binary-i386/
# deb cdrom:[Ubuntu 12.04.1 LTS _Precise Pangolin_ - Release amd64 (20120823.1)]/ precise main restricted

Revision history for this message
Brian Murray (brian-murray) wrote :

I tried recreating this with by passing -c (the path to an apt CD) to the trusty binary but was unsuccessful. However, looking in my log files I noticed the following:

2014-11-12 14:31:29,892 DEBUG AptCdrom.add() called with '/media/cdrom'

This doesn't appear in any of the duplicates log files so its probably not the right way to create the bug.

Revision history for this message
mateolan (mateolan) wrote :

@Brian Murray, when this happened to me, I was not trying to upgrade via cdrom or DVD, i was trying to upgrade via command:

sudo do-release-upgrade

When I look at my sources.list it is true that my cdrom lines are commented out.

However, I hope this isn't the expected result of commenting-out those lines...right?

Changed in update-manager (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Medium
Revision history for this message
cavh (ubuntu-cvh) wrote :

I encountered this bug on trying to upgrade from Precise to Trusty and was able to move on from this error by deselecting all those PPAs (by means of the graphical interface) which referred to 'precise' as the distribution.

I then ran 'sudo do-release-upgrade' and the upgrade proceeded as usual.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.