Upgrade to 18.10 fails: Please install all available updates

Bug #1799319 reported by Guy Rouillier
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I just tried to upgrade an x64 VM from 18.04 Mate to 18.10, and it failed. Using the Software Updater from the menu, it tells me

"The software on this computer is up to date. However, Ubuntu 18.10 is now available (you have 18.04)."

When I click the Upgrade... button, the dialog disappears and nothing happens.

If I run do-release-upgrade from a terminal, it tells me

"root@ubuntu64:~# do-release-upgrade
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading."

I have dual boot on this computer, and also have Ubuntu Mate 18.04 running as a bootable OS. I just tried to upgrade that installation, and it fails in exactly the same way. I only recently installed that instance, so it's a very simple installation at this point (unlike the VM which I've used for several years and installed numerous packages, including PPA.) So there appears to be a general problem in this upgrade path.

Revision history for this message
Guy Rouillier (guy-rouillier) wrote :

I got some help on this in the original bug report I started with:

https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799009

Manually running apt update - apt upgrade resulted in about a dozen packages getting updated. This was after Software Updater told me my system was up to date, but a new release was available. So, the core issue appears to be that Software Updater is missing updates that are only detected by manually running apt update.

After running apt update - apt upgrade, I am now in the process of running do-release-upgrade.

Revision history for this message
Guy Rouillier (guy-rouillier) wrote :

I mentioned I have dual boot, and was experience the same issue in the top-level bootable Ubuntu Mate 18.04 installation. I'm there now. I applied the latest updates, including one to software updater, but still had the same issue I described above: software updater told me my system was up to date, but do-release-upgrade told me to install available updates. This time, I took some notes. After running sudo apt update, I then ran

  apt list --upgradable

Here is the resulting list:

libnautilus-extension1a/bionic-updates 1:3.26.4-0~ubuntu18.04.1 amd64 [upgradable from: 1:3.26.3-0ubuntu4]

man-db/bionic-updates 2.8.3-2ubuntu0.1 amd64 [upgradable from: 2.8.3-2]

ubuntu-mono/bionic-updates,bionic-updates 16.10+18.04.20181005-0ubuntu1 all [upgradable from: 16.10+18.04.20180421.1-0ubuntu1]

unattended-upgrades/bionic-updates,bionic-updates 1.1ubuntu1.18.04.6 all [upgradable from: 1.1ubuntu1.18.04.5]

After applying these updates, now running "do-release-upgrade" starts the upgrade process. I don't know if there is anything significant about these 4, or just the fact that *any* updates are available. The problem remains in that software updater is not finding them.

no longer affects: ubuntu-mate
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
Brian Murray (brian-murray) wrote :

This was likely fixed (its hard to tell without log files) with the following upload of ubuntu-release-upgrader for cosmic.

ubuntu-release-upgrader (1:18.10.11.1) cosmic; urgency=medium

  * DistUpgrade/DistUpgradeController.py: check all the python symlinks and
    versions instead of the python one. Thanks to juliank for the assistance.
    (LP: #1799839)
  * do-release-upgrade: Do not block release upgrades if the installable
    updates are ones which are not fully phased. (LP: #1799710)

 -- Brian Murray <email address hidden> Wed, 31 Oct 2018 16:15:17 -0700

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Guy Rouillier (guy-rouillier) wrote :

I was wondering how I could possible recreate this scenario. Coincidentally, I received your update on the same day I learned that 19.04 was available. So, I started up the VirtualBox VM containing Ubuntu Mate 18.10. I got a pop up telling me that 19.04, and asking if I would like to upgrade. I hadn't started this VM in over a week, so I ran Software Updater to check for updates. Some were available, so I installed them first. Once finished, I closed Software Updater, then clicked the Upgrade button on the original popup. The popup disappeared and nothing happened! So, I'm back in this same situation as I was when I first reported this issue.

I tried rebooting so the updates applied by Software Updater were running. The same thing is happening. I run Software Updater; it reports no updates are available, but a new version is available. When I click the upgrade button, Software Updater disappears and nothing happens.

I'm going to shut down the VM and back it up, so I can repeat this scenario. Please let me know what steps you'd like me to take.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

Sorry, I missed your previous messages. If you still have this system available for testing please include the output of the command 'apt-cache policy ubuntu-release-upgrader'. Then please run 'DEBUG_UPDATE_MANAGER=1 do-release'. Thanks in advance!

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Guy Rouillier (guy-rouillier) wrote :

Brian, thanks for the reply. I didn't get notified so I missed your reply. I used my workaround to eventually update the VM, so I can no longer test the failed upgrade. I'll try to remember if this happens again. Here is the output of the command you requested:

guyr@ubuntu64:~$ apt-cache policy ubuntu-release-upgrader-core
ubuntu-release-upgrader-core:
  Installed: 1:19.04.16.6
  Candidate: 1:19.04.16.6
  Version table:
 *** 1:19.04.16.6 500
        500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1:19.04.16 500
        500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages

Revision history for this message
Jeff Abrahamson (jeff-purple) wrote :

I believe this bug affects me as well.

I see this:

jeff@starshine:~ $ apt-cache policy ubuntu-release-upgrader-gtk
ubuntu-release-upgrader-gtk:
  Installed: 1:18.04.34
  Candidate: 1:18.04.34
  Version table:
 *** 1:18.04.34 500
        500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1:18.04.17 500
        500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        500 http://es.archive.ubuntu.com/ubuntu bionic/main i386 Packages
jeff@starshine:~ $ DEBUG_UPDATE_MANAGER=1 do-release-upgrade
Checking for a new Ubuntu release
MetaRelease.__init__() useDevel=False useProposed=False
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release-lts
/etc/update-manager/meta-release: -development
/etc/update-manager/meta-release: -proposed
metarelease-uri: https://changelogs.ubuntu.com/meta-release
MetaRelease.download()
reading file '/home/jeff/.cache/update-manager-core/meta-release'
have self.metarelease_information
MetaRelease.parse()
current dist name: 'bionic'
found distro name: 'warty'
found distro name: 'hoary'
found distro name: 'breezy'
found distro name: 'dapper'
found distro name: 'edgy'
found distro name: 'feisty'
found distro name: 'gutsy'
found distro name: 'hardy'
found distro name: 'intrepid'
found distro name: 'jaunty'
found distro name: 'karmic'
found distro name: 'lucid'
found distro name: 'maverick'
found distro name: 'natty'
found distro name: 'oneiric'
found distro name: 'precise'
found distro name: 'quantal'
found distro name: 'raring'
found distro name: 'saucy'
found distro name: 'trusty'
found distro name: 'utopic'
found distro name: 'vivid'
found distro name: 'wily'
found distro name: 'xenial'
found distro name: 'yakkety'
found distro name: 'zesty'
found distro name: 'artful'
found distro name: 'bionic'
found distro name: 'cosmic'
found distro name: 'disco'
new dist: <UpdateManager.Core.MetaRelease.Dist object at 0x7fbe1e6a0ba8>
Please install all available updates for your release before upgrading.
1, jeff@starshine:~ $

Revision history for this message
Jeff Abrahamson (jeff-purple) wrote :

And, just to be complete:

jeff@starshine:~ $ sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get autoremove -y && sudo apt-get dist-upgrade -y && sudo apt-get autoremove -y
Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:2 http://es.archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://es.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://es.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:5 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libboost-dev
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libboost-dev
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
jeff@starshine:~ $

Revision history for this message
Guy Rouillier (guy-rouillier) wrote :

I just encountered this exact same scenario running Ubuntu Mate 19.04. Software Updater believes all updates have been applied. I get the pop-up saying 19.10 is available, I click the Upgrade button, and the dialog disappears and nothing happens. Again, I drop to a command prompt:

root@ubuntu64:~# do-release-upgrade
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

root@ubuntu64:~# apt-get upgrade (following update)
The following packages were automatically installed and are no longer required:
  liblldb-8 llvm-8 llvm-8-dev llvm-8-runtime
Use 'apt autoremove' to remove them.
The following packages have been kept back:
  lldb
The following packages will be upgraded:
  gnome-shell gnome-shell-common

root@ubuntu64:~# do-release-upgrade
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

root@ubuntu64:~# apt-get purge lldb
Removing lldb (1:7.0-43ubuntu1) ...

And now do-release-upgrade is proceeding.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

Neither gnome-shell nor gnome-shell-common are currently phasing so that is not the issue. Perhaps there is a disconnect between what update-manager thinks is available and what apt does? Or maybe the pop up regarding release upgrades raises even if do-release-upgrade won't run.

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

It does seem that check-new-release-gtk will silently exit if there are available updates. However, if you run it via the command line you'll see the error.

 $ /usr/lib/ubuntu-release-upgrader/check-new-release-gtk -d
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

So the next step would be to see if the thing that calls check-new-release-gtk is aware of whether there are updates available.

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

Well this should have been fixed with this upload:

ubuntu-release-upgrader (1:18.10.11) cosmic; urgency=medium

  * do-release-upgrade: do not run the release upgrade if either not all
    updates are installed or a reboot is required due to a libc6 upgrade.
    (LP: #1797209)
  * debian/control: change ubuntu-release-upgrader-core to depend on
    ca-certificates (LP: #1796940)
  * Update of demotions and mirrors data.

 -- Brian Murray <email address hidden> Wed, 10 Oct 2018 14:10:29 -0700

Revision history for this message
Guy Rouillier (guy-rouillier) wrote :

Brian, thanks for the responses. Please see my last action:

root@ubuntu64:~# apt-get purge lldb

This allowed do-release-upgrade to finally proceed. gnome-shell and gnome-shell-common were wild gooses. The key ingredient seems to be this:

root@ubuntu64:~# apt-get upgrade
The following packages have been kept back:
  lldb

Once I purged lldb, the release upgrade was clear to go. So, the hiccup seems to be held-back packages. I don't know enough about the inner workings of the upgrade process to understand how held-back packages figure into it.

Revision history for this message
Guy Rouillier (guy-rouillier) wrote :

I had forgotten I had submitted this bug report, and just encountered this same issue when I upgraded from 21.04 to 21.10. I reported my problem with this latest upgrade on the Ubuntu Mate Community forum. At least I'm consistent: the post there reads almost exactly like my bug report here. :)

See details here:

https://ubuntu-mate.community/t/prompt-to-upgrade-21-04-to-21-10-does-nothing/24672

This is a little disheartening that the same issue continues 2 1/2 years later.

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

Other bug subscribers