MAAS 1.9 fails to upgrade in some scenarios
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
1.9 |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
System is Trusty in a VM, 1 CPU, 4 GB Ram, 38 GB disk.
sudo add-apt-repository ppa:maas/next
sudo apt-get update
sudo apt-get install maas
Install proceeded until the following error:
Error in migration: maasserver:
Traceback (most recent call last):
File "/usr/sbin/
main()
File "/usr/sbin/
run()
File "/usr/sbin/
management.
File "/usr/lib/
utility.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
output = self.handle(*args, **options)
File "/usr/lib/
ignore_ghosts = ignore_ghosts,
File "/usr/lib/
success = migrator.
File "/usr/lib/
result = migrator.
File "/usr/lib/
result = self.migrate(
File "/usr/lib/
result = self.run(migration)
File "/usr/lib/
return self.run_
File "/usr/lib/
migration_
File "/usr/lib/
return (lambda: direction(orm))
File "/usr/lib/
node.
File "/usr/lib/
boot_
File "/usr/lib/
for subnet in self.vlan.
File "/usr/lib/
rel_obj = qs.get()
File "/usr/lib/
num = len(clone)
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
for row in compiler.
File "/usr/lib/
for rows in self.execute_
File "/usr/lib/
cursor.
File "/usr/lib/
return self.cursor.
File "/usr/lib/
six.
File "/usr/lib/
return self.cursor.
django.
LINE 1: ...erver_
=====
Version info:
ubuntu@
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
iU maas 1.9.0~rc1+
ii maas-cert-server 0.2.11-
ii maas-cli 1.9.0~rc1+
ii maas-cluster-
ii maas-common 1.9.0~rc1+
ii maas-dhcp 1.9.0~rc1+
ii maas-dns 1.9.0~rc1+
ii maas-proxy 1.9.0~rc1+
iF maas-region-
ii maas-region-
ii python-django-maas 1.9.0~rc1+
ii python-maas-client 1.9.0~rc1+
ii python-
ubuntu@
===
tar of /var/log/maass/* included.
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 98 lines (+67/-13)1 file modifiedsrc/maasserver/migrations/0182_initial_networking_layout.py (+67/-13)
- Blake Rouse (community): Approve
-
Diff: 98 lines (+67/-13)1 file modifiedsrc/maasserver/migrations/0182_initial_networking_layout.py (+67/-13)
Changed in maas: | |
importance: | Undecided → Critical |
milestone: | none → 1.9.0 |
Changed in maas: | |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
status: | Triaged → In Progress |
summary: |
- MAAS 1.9 fails install + MAAS 1.9 fails to upgrade in some escenarios |
Changed in maas: | |
assignee: | Mike Pontillo (mpontillo) → Blake Rouse (blake-rouse) |
Changed in maas: | |
milestone: | 1.9.0 → next |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
milestone: | next → none |
In case anyone needs a workaround before the final fix for this, I want to point out that this only affects the upgrade path if there are nodes in READY state. Therefore, a possible workaround is:
"sudo maas-region-admin dbshell"
followed by
"update maasserver_node set status=8 where status=4;"
This process will mark any READY nodes BROKEN. It's likely that nodes will need to be recommissioned after doing this before they can be deployed.