piston3 package is unnecessarily distro-specific (MAAS breaks after do-release-upgrade from focal to jammy)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Medium
|
Unassigned |
Bug Description
Upgrading from MAAS 3.2 to 3.3 requires also upgrading from Focal to Jammy. The PPA for MAAS 3.2 only supports Focal and the PPA for MAAS 3.3 only supports Jammy.
After you upgrade from Focal to Jammy, MAAS is broken until you also upgrade it. This doesn't work (by default) in one step because there are 2 different PPAs.
The main reason it breaks is that the 3.2/focal python3-
This is simply due to a missing "--with python3" in debian/rules, which would allow the package to continue working for the brief period until the MAAS 3.3 upgrade is started because the files will be in the version-agnostic path (where they should be).
ModuleNotFoundE
Traceback (most recent call last):
File "/usr/sbin/
load_
File "/usr/lib/
runMasterSe
File "/usr/lib/
runService(
File "/usr/lib/
UnixApplica
File "/usr/lib/
self.
File "/usr/lib/
ser = plg.makeService
File "/usr/lib/
self.
File "/usr/lib/
django.setup()
File "/usr/lib/
apps.
File "/usr/lib/
app_config = AppConfig.
File "/usr/lib/
import_
File "/usr/lib/
return _bootstrap.
File "<frozen importlib.
File "<frozen importlib.
File "<frozen importlib.
Related branches
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 13 lines (+1/-1)1 file modifieddebian/rules (+1/-1)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 3.5.0 |
Merge Proposal: /code.launchpad .net/~lathiat/ django- piston3/ +git/django- piston3/ +merge/ 445720
https:/