maas regiond upgrade from 1.8.2 to 1.9.1 silently failed

[James Troup]

The MAAS controller for ProdStack 4½ was upgraded (by Landscape) from 1.8.2 to 1.9.1 and the upgrade process for maas-regiond seems to have silently failed as the machine still has a /etc/maas/maas_local_settings.py but no /etc/maas/regiond.conf

The term.log history of the upgrade is available here:

  https://pastebin.canonical.com/151650/

root@chenet:~# dpkg -l maas\* | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===========================================================-=====================================-============-===============================================================================
ii maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Server minimum region controller
root@chenet:~#

[Marc H. (marc-hofstetter)]

hi all, ist there any update on this issue? I ran into the same problem.

The regiond.conf was createt but the upgrade process can no longer connect to the PostgreSQL Database...

django.db.utils.OperationalError: FATAL: password authentication failed for user "maas"
FATAL: password authentication failed for user "maas"

[Paul Gear (paulgear)]

FWIW, this bug also resulted in an unrestartable maas-regiond and maas-clusterd, since their config files were empty. I had to manually create the contents of those files using another MAAS server as a template.

[Andres Rodriguez (andreserl)]

Ok, I've tried to reproduce this upgrade path over an over but can't manage to reproduce it. My upgrade results in:

ubuntu@maas01:~$ ls -l /etc/maas/
total 36
-rw-r----- 1 root maas 83 Apr 28 15:18 clusterd.conf
-rw-r--r-- 1 root root 5135 Oct 14 2015 drivers.yaml
-rw-r----- 1 root maas 341 Apr 28 15:06 maas_cluster.conf.maas-old
-rw-r----- 1 root maas 737 Apr 28 15:08 maas_local_settings.py.maas-old
drwxr-xr-x 2 root root 4096 Apr 28 15:18 preseeds
-rw-r--r-- 1 root root 683 Oct 16 2015 pserv.yaml.maas-old
-rw-r----- 1 root maas 130 Apr 28 15:18 regiond.conf
drwxr-xr-x 9 root root 4096 Apr 28 15:05 templates

[Andres Rodriguez (andreserl)]

We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.