Comment 1 for bug 2041854

Looking at the logs, there are several things going on here. First there's this:

  okt 29 22:25:10 maas-system-maas sh[12958]: maasserver.listener: [info] Listening for database notifications.

This means that MAAS was still starting up when the migrate call was made, which means that it might miss the sys_vault_migration notification.

It does seem that in this case, MAAS did get the notification, since further down in the logs we can see:

  okt 29 22:25:15 maas-system-maas sh[12655]: maasserver.eventloop_12655.master: [info] Restarting region
  ...
  okt 29 22:25:41 maas-system-maas sh[12655]: maasserver.eventloop_12655.master: [info] Region restarted

So the region got restarted, but it took almost 30 seconds.

I'm also not sure about the way it checks for regions that have been restarted/stopped. It checks for region controllers that don't have any processes. But what's preventing the region from starting processes as it restarts?