Migration hang with defunct process when upgrading from 1.7.1 to 1.7.2rc1

[Adam Collard]

Following on from bug 1428041 dpkg just hangs:

Setting up maas-region-controller (1.7.2~rc1+bzr3350-0ubuntu1~trusty2) ...
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.contrib.contenttypes
 > django.contrib.sessions
 > django.contrib.sites
 > django.contrib.messages
 > django.contrib.staticfiles
 > piston
 > south

Not synced (use migrations):
 - maasserver
 - metadataserver
(use ./manage.py migrate to migrate these)
Traceback (most recent call last):
  File "/usr/sbin/maas-region-admin", line 16, in <module>
    management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/dist-packages/south/management/commands/migrate.py", line 107, in handle
    ignore_ghosts = ignore_ghosts,
  File "/usr/lib/python2.7/dist-packages/south/migration/__init__.py", line 199, in migrate_app
    applied_all = check_migration_histories(applied_all, delete_ghosts, ignore_ghosts)
  File "/usr/lib/python2.7/dist-packages/south/migration/__init__.py", line 88, in check_migration_histories
    raise exceptions.GhostMigrations(ghosts)
south.exceptions.GhostMigrations:

 ! These migrations are in the database but not on disk:
    <maasserver: 0115_unique_boot_source_selections>
    <maasserver: 0116_unique_boot_source_selections>
    <maasserver: 0117_delete_duplicate_config>
    <maasserver: 0118_config_key_unique>
    <maasserver: 0119_migrate_invalid_network_names>
    <maasserver: 0120_make_macaddress_node_nullable>
 ! I'm not trusting myself; either fix this yourself by fiddling
 ! with the south_migrationhistory table, or pass --delete-ghost-migrations
 ! 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-controller:all maas-region-controller:all maas:all
15953 pts/5 S+ 0:00 | \_ /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/maas-region-controller.postinst configure 1.7.1+bzr3341-0ubuntu1~trusty1
15960 pts/5 Z+ 0:00 | \_ [maas-region-con] <defunct>

[Raphaël Badin (rvb)]

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.

[Raphaël Badin (rvb)]

Looks like a packaging problem: the migrations in question are *not* present in the package that used to be (?) in the testing PPA (1.7.2~rc1+bzr3350-0ubuntu1~trusty2) but they *are* present in the upstream code (1.7 revision 3350).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.