Migration hang with defunct process when upgrading from 1.7.1 to 1.7.2rc1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Following on from bug 1428041 dpkg just hangs:
Setting up maas-region-
rsyslog stop/waiting
rsyslog start/running, process 16010
* Stopping web server apache2
*
* Restarting PostgreSQL 9.3 database server
...done.
Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Module expires already enabled
Module wsgi already enabled
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)
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).
ps shows a defunct process
15934 pts/5 Ss+ 0:00 | \_ /usr/bin/dpkg --status-fd 69 --configure maas-cluster-
15953 pts/5 S+ 0:00 | \_ /usr/bin/perl -w /usr/share/
15960 pts/5 Z+ 0:00 | \_ [maas-region-con] <defunct>
tags: | added: landscape |
Changed in maas: | |
status: | New → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in ubuntu: | |
status: | Confirmed → Fix Released |
status: | Fix Released → Invalid |
Changed in ubuntu: | |
status: | Invalid → Fix Released |
This is bug 1427969 that Andres filed but then marked as Invalid because he thought his environment had a problem. I'm trying to reproduce the problem now.