It looks like that particular migration (0121_recompute_storage_size) assumes that this table under 'metadataserver' has already been migrated. However, when going directly to 1.8 from 1.5, this isn't the case.
A possible workaround may be to upgrade from 1.5.x to 1.7.x (available in trusty-updates), and then upgrade to 1.8.x.
I can think of a few possible fixes:
- Migration order should be enforced where dependencies like this exist
- Migrations under 'maasserver' should not depend on 'metadataserver'
- Move logic for recomputing storage size out of migrations
It looks like that particular migration (0121_recompute _storage_ size) assumes that this table under 'metadataserver' has already been migrated. However, when going directly to 1.8 from 1.5, this isn't the case.
A possible workaround may be to upgrade from 1.5.x to 1.7.x (available in trusty-updates), and then upgrade to 1.8.x.
I can think of a few possible fixes:
- Migration order should be enforced where dependencies like this exist
- Migrations under 'maasserver' should not depend on 'metadataserver'
- Move logic for recomputing storage size out of migrations