Comment 10 for bug 1908552

Ok, I think I see what's going on here. the .30 host successfully sets up MAAS and starts up. Then it fails, since maasserver_routable_pairs doesn't exist. Note that this is a view, and not a table.

What happens next is that the .31 runs 'maas init' and tries to run all the db migrations. The first thing it does is to drop all views. After that it should run all the migrations, and recreate the views, but it deadlocks somehow with the running .30 instance.

On the MAAS side, we could check to confirm whether any migrations need to be run, and don't do anything if the DB already has all the migration.

To work around it in FCE, you'd first have to stop MAAS after each 'maas init', and the restart them when everything is set up.