Comment 6 for bug 1676992

Looking at the log, I strongly suspect this bit is the culprit:

...
Mar 28 20:12:32 in-target: Running in chroot, ignoring request.
Mar 28 20:12:32 in-target: ^M
Mar 28 20:12:32 in-target: invoke-rc.d: policy-rc.d denied execution of restart.^M
Mar 28 20:12:32 in-target: Setting up maas-region-controller (2.2.0~beta3+bzr5815-0ubuntu1) ...
Mar 28 20:12:32 in-target: ^M
Mar 28 20:12:34 in-target: /usr/sbin/policy-rc.d returned 101, not running 'restart postgresql'^M
Mar 28 20:12:34 in-target: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf
Mar 28 20:12:34 in-target: ^M
Mar 28 20:12:34 in-target: ^M

Basically, Postgres is not (re)started, so MAAS has nothing to go against. I guess we need to figure out how we can perform a lazy model setup with Postgres not available, or restart Postgres ourselves before attempting to do model changes.