Crash during upgrade from Mantic to Noble due to Python 3.12

[Skia]

Upgrading from Mantic to Noble often triggers a crash related to Python 3.12 compatibility:
```
Traceback (most recent call last):
  File "/usr/sbin/update-apt-xapian-index", line 66, in <module>
    import axi.indexer
  File "/usr/lib/python3/dist-packages/axi/indexer.py", line 27, in <module>
    import imp
ModuleNotFoundError: No module named 'imp'
```

I guess that the crash happens when the indexer code is called while still being in the Mantic version, but the default Python3 package has already been upgraded to 3.12. However, that situation doesn't happen all the time, and the upgrade is sometimes able to complete without crash.

For some reasons, I mostly (only?) see this on Kubuntu upgrades.

Maybe that situation could also happen while upgrading from Jammy, but as the upgrade is currently broken due to some other issues, I haven't seen it yet.

[Brian Murray (brian-murray)]

During the Foundations team meeting we talked about adding a quirk to "turn off" a-x-i.

[Nick Rosbrook (enr0n)]

From what I can tell, there is not a systemd service or anything calling update-apt-xapian-index (there were comments in the IRC meeting[1] that suggested that). So is the idea here to just tell apport to ignore crash reports for /usr/sbin/update-apt-xapian-index during the upgrade? We already do the same thing for tracker-extract-3[2].

[1] https://irclogs.ubuntu.com/2024/03/21/%23ubuntu-meeting.html
[2] https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2049907

[Brian Murray (brian-murray)]

From what I can recall of the meeting there was a more general idea of stopping all systemd user services and cronjobs tha could fall over during a distribution upgrade. For this specific problem we can either stop running update-apt-xapian-index or just suppress the crashes.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-release-upgrader - 1:24.04.14

---------------
ubuntu-release-upgrader (1:24.04.14) noble; urgency=medium

  [ Brian Murray ]
  * Set prompt to lts because 24.04 is one (LP: #2061214)

  [ Nick Rosbrook ]
  * DistUpgradeQuirks: tell apport to ignore update-apt-xapian-index
    (LP: #2058227)
  * DistUpgradeQuirk: fix check for linux-image-raspi in cache (LP: #2061181)
  * DistUpgradeQuirks: handle t64 replacement packages (LP: #2061175)
  * Run pre-build.sh: updating mirrors, demotions, and translations.

 -- Nick Rosbrook <email address hidden> Mon, 15 Apr 2024 15:02:26 -0400

[Saurabh Minni (the100rabh)]

When can we expect this change to unblock upgrade from Mantis to Noble. https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043

[Skia (hyask)]

A quirk has been added to ubuntu-release-upgrader so this issue doesn't appear anymore, and upgrades from Mantic to Noble are already enabled.

[Saurabh Minni (the100rabh)]

That is weird, when I try release upgrade it shows the following. Its a

```
$ sudo do-release-upgrade -m desktop
Checking for a new Ubuntu release
No new release found.
```

I am on Mantic right now

```
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 23.10"
NAME="Ubuntu"
VERSION_ID="23.10"
VERSION="23.10 (Mantic Minotaur)"
VERSION_CODENAME=mantic
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=mantic
LOGO=ubuntu-logo
```

[Skia (hyask)]

Yes, sorry, I got confused, upgrades from Mantic are still hidden behind the `-d` flag. That means you need `do-release-upgrade -d` to get it.
Be advised though that if it's not enabled yet, there might be remaining issues that I'm not aware of, even if from my point of view, the jump from Mantic to Noble has been pretty much stabilized.

[Joe Fullmer (chssaddct)]

It's just that this bug is listed as the only blocker on the Release Status Tracking page:

https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043#current-blockers-for-enabling-upgrades-from-mantic-6

[Vitaliy Kanev (vitalkanev)]

In reply to Comment #10

Apparently not. According to release notes [1], there are more critical bugs blocking the Mantic to Noble upgrades. This include the libglib transitional package with Y2038 handling [2] and Thunderbird DEB-to-Snap conversion [3]

[1]: https://discourse.ubuntu.com/t/noble-numbat-release-notes/39890
[2]: https://pad.lv/2063221
[3]: https://pad.lv/2061918

[Jarl (jarl-dk)]

So, what you are saying is that https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043 needs an update, right?

[Tim Richardson (tim-richardson)]

the issues in Comment #10 appear to be closed, and they are not mentioned anyway on https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043
so it is confusing.

[Nibl (graystripe)]

I'm not sure what's blocking it either, I just know that I still can't upgrade from Mantic and don't feel comfortable forcing it just in case something is critically broken that isn't listed there. The confusion around what is and isn't blocking the upgrade involving some bugs that were listed as hard to recover from this time around has me erring on the side of caution.

https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043 lists https://pad.lv/2058227 as the only blocker, but the fix for that was released despite its status there being listed as only committed.
Meanwhile https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890#heading--known-issues just says upgrades are not supported, does not elaborate, but lists https://pad.lv/2063221 as one example, which is also fixed. If there are other critical issues blocking the upgrade, they should be listed too so users don't inadvertently bork their systems assuming it was safe to upgrade because the listed bugs were fixed.

[AmirR. H. (amirrh6)]

AFAIK Starting from May's 24th, Upgrades from Mantic have been enabled.