Upgrading Ubuntu Jammy to Ubuntu Noble fails with error message

[Leó Kolbeinsson]

Testing upgrading Ubuntu Jammy Desktop to Ubuntu Noble Desktop fails with error message:

Oh No! Something has gone wrong.
Aproblem has occurred and the system cannot recover.
Please contact system administrator ....etc.etc.

This was tested on 2 baremetal machines and both failed.

Attempted to boot back into system to no avail. Unable to access anything on the disk drives thus cannot send any further info .. attached is screen shot of the error message.

The command to upgrade was . sudo update-manager -d -c as per the testcases.

Test results here:
https://iso.qa.ubuntu.com/qatracker/milestones/450/builds/299392/testcases/1635/results

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2061228

[Brian Murray (brian-murray)]

This is not a screenshot I would have associated with update-manager or ubuntu-release-upgrader. Could you please run 'apport-collect 2061228' from one of the systems which failed to upgrade?

[Leó Kolbeinsson (leok)]

@brian-murray Brian Murray

Sorry but no way to run apport-collect as the systems do not boot after the failure (crash). When attempting to reboot the same screen shot appears instead of the desktop.

[Leó Kolbeinsson (leok)]

@brian-murray

Also tried to enter recovery mode - but was unable to run "apport-collect" as it failed to connect to launchpad (no network?)

pls advise

[Daniel van Vugt (vanvugt)]

Please check your mutter package versions per bug 2060423.

[Daniel van Vugt (vanvugt)]

It could also be bug 2054761 so check the journal for messages similar to that one.

[Leó Kolbeinsson (leok)]

@vanvugt yes this is a duplicate of 2054761 as far can be determined.

[Vale (valerauko)]

Same issue here.

After dpkg --configure -a in recovery mode I was able to boot normally, however no domain names could be resolved. Turns out systemd-resolved was uninstalled. Installing it back at least got DNS back working.

I have no idea what might be broken by this or even how to check if something is left dangling.

[Robert Los (robert-robertlos)]

Got the same or similar error. While doing a do-release-update from 22.04 to 24.04 it crashed halfway the installation of packages. After rebooting could only get a terminal window using ctrl-alt-F2. I tried to do a dpkg --configure -a but that feild due to too many errors. It turned out that networking did not work because the resolv wa not there. I do not know how to reinstall that.