Upgrade MAAS from 2.4 to 2.5 version - with "Ubuntu extra architectures" changed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Hi,
As stated on https:/
from MAAS version: 2.4.2 (7034-g2f5deb8b
to MAAS version: 2.5.2 (7523-ge4ecbd54
I get the following error:
Setting up maas-region-
Operations to perform:
Apply all migrations: auth, contenttypes, maasserver, metadataserver, piston3, sessions, sites
Running migrations:
Applying maasserver.
Applying maasserver.
Applying maasserver.
Applying maasserver.
Applying maasserver.
Applying maasserver.
File "/usr/lib/
"__main__", mod_spec)
File "/usr/lib/
exec(code, run_globals)
File "/usr/lib/
raise SystemExit(
File "/usr/lib/
management.
File "/usr/lib/
utility.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
output = self.handle(*args, **options)
File "/usr/lib/
fake_
File "/usr/lib/
return command.
File "/usr/lib/
output = self.handle(*args, **options)
File "/usr/lib/
fake_
File "/usr/lib/
state = self._migrate_
File "/usr/lib/
state = self.apply_
File "/usr/lib/
state = migration.
File "/usr/lib/
operation.
File "/usr/lib/
self.
File "/usr/lib/
url='http://
File "/usr/lib/
return getattr(
File "/usr/lib/
self.
__fake_
dpkg: error processing package maas-region-
installed maas-region-
dpkg: dependency problems prevent configuration of maas:
maas depends on maas-region-
Package maas-region-
dpkg: error processing package maas (--configure):
dependency problems - leaving unconfigured
The steps that I follow to repreduse the failure:
1. Create a new container:
lxc-create -n maas -t download -- -d ubuntu -a amd64 -r bionic
2. start the container
lxc-start -n maas
3. Attache the container
lxc-attach -n maas su
4. update the apt
apt update
5. install maas
apt install maas
6. create maas user
7. change the repo
setting -> "package repositories" -> "Ubuntu extra architectures" set the URL to: http://
8. install add-apt-repository
sudo apt-get install software-
9. add ppa:maas/stable
add-apt-
10. upgrade the packages:
apt upgrade
root@maas:~# dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
iU maas 2.5.2-7523-
ii maas-cli 2.5.2-7523-
un maas-cluster-
ii maas-common 2.5.2-7523-
ii maas-dhcp 2.5.2-7523-
un maas-dns <none> <none> (no description available)
ii maas-proxy 2.5.2-7523-
ii maas-rack-
ii maas-region-api 2.5.2-7523-
iF maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.5.2-7523-
ii python3-maas-client 2.5.2-7523-
ii python3-
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
I hit this issue as well during my upgrade. Since I don't need any other architectures than x86, I edited /usr/lib/ python3/ dist-packages/ maasserver/ migrations/ builtin/ maasserver/ 0166_auto_ select_ s390x_extra_ arches. py and basically stubbed out the add_s390x_ to_pkg_ repository_ to_arches( ) function, ran apt-update -y again, and the upgrade finished up just fine.
It's not a "solution" but if you are reading this because you hit the same issue, it's a viable workaround to get you out of trouble.