line 9 of maas-region-controller.postrm tests for the existence of '/etc/dbconfig-common/maas.conf', which will not exist. the file that gets created is instead maas-region-controller.conf. since that test is never true, the call to dbc_go to do the postrm.pgsql stuff never happens.
This appears to contribute to some flakiness involving purging and reinstalling maas.
On one server that I'm currently having difficulty with, I had a /etc/dbconfig-common/maas-region-controller.conf that was two months (and several maas versions) old, despite having purged several times.
I think this is related to the error messages I was seeing when purging, including errors about wrong password for user maas. The local_settings.py I saw had a password of 'maas', but that .conf file had a different password.
line 9 of maas-region- controller. postrm tests for the existence of '/etc/dbconfig- common/ maas.conf' , which will not exist. the file that gets created is instead maas-region- controller. conf. since that test is never true, the call to dbc_go to do the postrm.pgsql stuff never happens.
This appears to contribute to some flakiness involving purging and reinstalling maas.
On one server that I'm currently having difficulty with, I had a /etc/dbconfig- common/ maas-region- controller. conf that was two months (and several maas versions) old, despite having purged several times.
I think this is related to the error messages I was seeing when purging, including errors about wrong password for user maas. The local_settings.py I saw had a password of 'maas', but that .conf file had a different password.