Upgrading to MAAS 1.7.1 to 1.7.2 causes migrations to fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Critical
|
Unassigned |
Bug Description
> django.
> piston
> south
Not synced (use migrations):
- maasserver
- metadataserver
(use ./manage.py migrate to migrate these)
Traceback (most recent call last):
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/
applied_all = check_migration
File "/usr/lib/
raise exceptions.
south.exception
! These migrations are in the database but not on disk:
<maasserver: 0115_unique_
<maasserver: 0116_unique_
<maasserver: 0117_delete_
<maasserver: 0118_config_
<maasserver: 0119_migrate_
<maasserver: 0120_make_
! I'm not trusting myself; either fix this yourself by fiddling
! with the south_migration
! to South to have it delete ALL of these records (this may not be good).
To reproduce:
1. sudo add-apt-repository ppa:maas-
2. sudo apt-get update && sudo apt-get install maas
3. sudo maas-region-admin createadmin
4. sudo add-apt-repository ppa:maas-
5. sudo apt-get update && sudo apt-get dist-upgrade.
Changed in maas: | |
importance: | Undecided → Critical |
description: | updated |
Changed in maas: | |
status: | New → Invalid |