Dear Simon,
thank you for your quick response. I filed this because it might improve Ubuntu which i have been using as my main system since 2004 and am very happy about. as to ## 3. It is ok that we have to wait until processes are stopped. I was expecting that the upgrade should require a reboot shortly after running a dist-upgrade and that cron processes are disabled or that a warning is given that some processes are still running which might block the upgrade. Or perhaps that a check is done before the upgrade of anacron. ## 4. I have several disks in my system, most are ext4 formatted. It looked like the bios/eufi settings were changed. i could recover by changing the boot sequence. ##6. Rabbit was running as infrastructure in my kubernetes cluster (k3s based) on the server. Should not effect an upgrade of a remaining rabbitmq installation (which was not started). ## 7. Thanks for the tip. I will include that in the ansible playbook that will upgrade my root servers and virtual machines Perhaps a warning in the do-release-upgrade that services might hinder a smooth upgrade can be shown and if possible a list of possible blocking processes be advised to stop manually before the update. Met vriendelijke groeten, kind regards and many thanks. dr. ir. Robert Los Robert Los Commercial and Contract Services B.V. Nachtegaallaan 46 3055 CS Rotterdam The Netherlands M:+31 6 24893872 E: [email protected] www.robertlos.nl <http://www.robertlos.nl> On 10/1/26 14:17, Simon Johnsson wrote: > I've investigated the upgrade logs now and concluded that this bug > report should rather be split up into multiple. > > ## 1. NVIDIA driver missing > > The NVIDIA driver userspace packages were marked for auto-removal as the > installed driver on Noble used the `-hwe-24.04` module flavor, which > does not have a Resolute successor. This is a genuine bug that the > Ubuntu Release Upgrader should consider, by for example adding ^nvidia- > driver-.* to the removal denylist. > > ## 2. sudo missing > > The sudo package in 26.04 uses an alternatives symlink to the > `/usr/bin/sudo` binary, where the sudo binary package links from > `/usr/bin/sudo.ws`. This means that during the upgrade, sudo will be > missing without a fallback until it completes. > > ## 3. anacron hang > > This is likely the fault of the anacron package itself. In its postinst, > it calls `deb-systemd-invoke restart anacron.service`, which is a batch > runner. While anacron executes `/etc/cron.daily/*` the unit cgroup is > busy. On this system, backup-manager is installed, which can run for > hours and thereby blocking the upgrade. One alternative is to drop the > restart in the postinst, or to use `deb-systemd-invoke --no-block`. > > ## 4. Dropped boot entries > > I cannot determine the cause based on the data we have to go by here, > however this is what we can say based on the logs: > > * grub-install ran correctly with no error output > * `/etc/default/grub` was chosen to keep the modified version, but I can't > reason about its contents > * Landing in `grub>` and not `grub rescue>` means that the core image + > normal.mod loaded, however no usable `grub.cfg` was found > * `/boot/grub/x86_64-efi/` was repopulated with 2.14 modules by > grub-efi-amd64-bin > > Based on this, we can infer that the likely causes are that there was a > stale GRUB binary, a duplicate ordering artefact in the firmware's boot > list, or a troublesome `/etc/default/grub` setting used in the locally > modified configuration. > > ## 5. MySQL package/configuration issue > > The transition from 8.0 -> 8.4 seems to be a resolver limitation. It > seems that Qt5 dragged in the libmysqlclient24 package, but the > transition was unable to complete so the runtime library was purged. In > this case the Ubuntu Release Upgrader could have surfaced a "held back" > packages blocking warning. > > ## 6. RabbitMQ issues > > Based on the provided logs, I cannot see any rabbitmq-server being > installed on this system. There *is* a PPA `canonical- > server/rabbitmq-3.13-noble` which got disabled during the sources > rewrite. The erlang-* packages got upgraded from the PPA's versions to > the archive's cleanly. Maybe this was running on the k3s cluster? > > There's also a `rabbitmq-port-forward.service' in the JournalErrors > which appears to have failed. All in all, this does not look like a > Ubuntu packaging bug. > > ## 7. Many interactive decisions > > In total I could see 8 interactive decisions, out of which 5 were dpkg > conffile prompts and 3 were full-screen debconf dialogs. These appeared > due to local modifications of the packages' configuration files. This > could have been run unattended with: > > $ do-release-upgrade -f DistUpgradeViewNonInteractive > > and DPkg::Options::--force-confold > > Everything is working as designed here, as the system's locally modified > configuration files would otherwise have been overwritten by the > packages' updated defaults. > > ## 8. Python 3.14 upgrade > > The system is using a hybrid between the deadsnakes PPA and the Ubuntu > archive. There may be issues with this, so consider running: > > $ apt install --reinstall libpython3.14-stdlib python3.14 > > to avoid unexpected issues. > > ## Summary > > In general for systems with this many third-party repos and packages, I > would recommend closing services like Kubernetes and such before > attempting the upgrade. Many of the issues experienced during the > upgrade were caused by third-party interactions, and not Ubuntu's core > setup itself. > > * MySQL seems to be broken on the system and requires a manual transition > from 8.0 to 8.4. > * If you provide the output of: > > $ sudo efibootmgr -v > > I can try to deduce why the system landed in the `grub>` shell > > Other than that, I will go ahead and file the corresponding bugs and > link them here :) > ** Attachment added: "rlccsbv-logo200.png" https://bugs.launchpad.net/bugs/2169124/+attachment/6004256/+files/rlccsbv-logo200.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2169124 Title: bad upgrade experience To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2169124/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
