MAAS "migrations" '0121_recompute_storage_size' fails 1.5.4 to 1.8.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Gavin Panella | ||
1.8 |
Fix Released
|
Critical
|
Gavin Panella |
Bug Description
* ULTS 14, had MAAS 1.5.4.
* Running over a cluster of 12 hosts, with Juju 1.24.5 handling a fairly static park of a few dozen instances.
After problems attempting to hand over "metal" from MAAS 1.5.4 to Juju 1.24.5 attempted upgrade to MAAS 1.8.0 after checking Changelog in
http://
that indicate some significant configuration changes in 1.7.0 and some more internal ones in 1.8.0 but no known upgrade difficulties. Option was 1.7.6 which is part of ULTS 14 'trusty-updates' archive, but since also running Juju 1.24.5 from PPA "stable" decided to go for PPA "stable" for MAAS too, and then follow configuration upgrades described in changelog. Looked at:
http://
The outcome is that one of the Django "migrations" fails as also described in:
http://
* Restarting PostgreSQL 9.3 database server
...done.
Syncing...
Creating tables ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Synced:
> django.contrib.auth
> django.
> django.
> django.
> django.
> django.
> piston
> south
Not synced (use migrations):
- maasserver
- metadataserver
(use ./manage.py migrate to migrate these)
Running migrations for maasserver:
- Migrating forwards to 0138_perf_
> maasserver:
Error in migration: maasserver:
Traceback (most recent call last):
......
File "/usr/lib/
return self.cursor.
django.
LINE 1: ..."."name", "metadataserver
Related branches
- Andres Rodriguez (community): Approve
- Blake Rouse (community): Approve
-
Diff: 14 lines (+4/-0)1 file modifiedsrc/maasserver/migrations/0121_recompute_storage_size.py (+4/-0)
- Mike Pontillo (community): Approve
-
Diff: 14 lines (+4/-0)1 file modifiedsrc/maasserver/migrations/0121_recompute_storage_size.py (+4/-0)
Changed in maas: | |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Gavin Panella (allenap) |
milestone: | none → 1.9.0 |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
BTW as described in an AskUbuntu related question I have checked the MAAS db directly and summarizing it with:
select parameters as "WoL" dhcplease as l macaddress as m macaddress_ networks as m2n
l.ip as "lease",
l.mac as "Ethernet",
w.name as "network",
n.hostname as "node",
n.storage as "storage",
n.power_
from
maasserver_
inner join maasserver_
on l.mac = m.mac_address
left join maasserver_
on m.id = m2n.macaddress_id
left join maasserver_network as w
on m2n.network_id = w.id
left join maasserver_node as n
on m.node_id = n.id
order by
n.hostname
(a query which may of general usefulness) the output looks consistent and complete, so the upgrade does not seem to have damaged the database. However the storage size for the 12 nodes reported is different for some, when they are all identical nodes. Some report 916913 and most report 1408. I can't easily related either to the size of the '/' filetree (800G) or the total storage (around 24TB).