16.04 to 18.04 do-release-upgrade fails with "Command terminated with exit status 1"

Bug #1787712 reported by Krisztian Andre
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Upgrade fails with:

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://ucho.ignum.cz/ubuntu xenial InRelease
Hit http://archive.canonical.com/ubuntu xenial InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command terminated with exit status 1 (Sat Aug 18 11:47:54 2018) ===

Revision history for this message
Krisztian Andre (akrisztian) wrote :
Revision history for this message
Krisztian Andre (akrisztian) wrote :

Installed packages attached. Sources.list.d is empty.

Revision history for this message
Krisztian Andre (akrisztian) wrote :

Replacing sources.list with the following fixed it
deb http://us.archive.ubuntu.com/ubuntu/ bionic main universe restricted multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ bionic main universe restricted multiverse

deb http://security.ubuntu.com/ubuntu bionic-security main universe restricted multiverse
deb-src http://security.ubuntu.com/ubuntu bionic-security main universe restricted multiverse

deb http://us.archive.ubuntu.com/ubuntu/ bionic-updates main universe restricted multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ bionic-updates main universe restricted multiverse

deb http://us.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse

Revision history for this message
Krisztian Andre (akrisztian) wrote :

correction: replace bionic with xenial

Revision history for this message
Vasilj Davidović (vasilj-davidovic) wrote :

I had same problem, replaced sources.list with suggested one (xenial instead of bionic) but still unable to upgrade

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command detached from window (Fri Jan 25 15:26:39 2019) ===
=== Command terminated with exit status 1 (Fri Jan 25 15:26:49 2019) ===

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

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

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
S. Jegen (s-jegen) wrote :

In my case I am trying to update from Ubuntu 18.04 to 18.10 and get the same behaviour (apart from the distribution name):

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://archive.ubuntu.com/ubuntu bionic InRelease
Hit http://archive.canonical.com/ubuntu bionic InRelease
Hit http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Ign http://dl.google.com/linux/chrome/deb stable InRelease
Hit http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit http://dl.google.com/linux/chrome/deb stable Release
Fetched 0 B in 6s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command terminated with exit status 1 (Sun Feb 10 17:52:44 2019) ===

Revision history for this message
BatulR (batulr-ridlr) wrote :

I am trying to upgrade from 16.04 to 18.04

apt-get update and apt-get upgrade command executed successfully after installing necessary packages suggested as resolutions to these commands

however sudo do-release-upgrade fails with following details

Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,240 kB]
Fetched 1,241 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting 'bionic.tar.gz'

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://in.archive.ubuntu.com/ubuntu xenial InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done

The log doesnt indicate what is missing.
How to Proceed?

Revision history for this message
Andrey Arapov (andrey-arapov) wrote :

I've had this issue:

# do-release-upgrade -f DistUpgradeViewNonInteractive
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1240 kB]
Fetched 1241 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting 'bionic.tar.gz'
  MarkInstall libpam-cap [ amd64 ] < none -> 1:2.25-1.2 > ( libs ) FU=1
No candidate ver: linux-image-4.4.0-131-generic
No candidate ver: linux-image-4.4.0-135-generic
No candidate ver: linux-image-extra-4.4.0-131-generic
No candidate ver: linux-image-extra-4.4.0-135-generic
No candidate ver: linux-signed-image-4.4.0-131-generic
No candidate ver: linux-signed-image-4.4.0-135-generic
# echo $?
1

Then it worked after I ran: apt-get autoremove

Not sure, though, whether that was the issue...
I'd rather blame that had something to do with the network/mirror.

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.