MAAS installation doesn't create database config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned |
Bug Description
MAAS leaves behind an empty database config, region controller fails to start
Purge databases and configs from previous install attempt
root@spoink:/etc# apt-get purge maas maas-dns maas-dhcp maas-proxy maas-region-
...
root@spoink:/etc# apt-get autoremove
...
root@spoink:/etc# ls -la /etc/bind /etc/maas /var/lib/maas
ls: cannot access /etc/maas: No such file or directory
ls: cannot access /var/lib/maas: No such file or directory
/etc/bind:
total 12
drwxr-sr-x 2 root 113 4096 Feb 1 16:47 .
drwxr-xr-x 100 root root 4096 Feb 1 16:47 ..
-rw-rw---- 1 root 113 890 Feb 1 16:00 named.conf.
root@spoink:/etc# rm -rf bind
Install maas:
root@spoink:~# apt-get install maas
...
Remove dnssec-validation duplicate config
root@spoink:~# vi /etc/bind/
root@spoink:~# sudo dpkg-reconfigure -fnoninteractive maas-dns
* Stopping domain name service... bind9
rndc: connect failed: 127.0.0.1#953: connection refused
...done.
* Starting domain name service... bind9
...done.
Check database config:
root@spoink:~# cat /etc/maas/
database_host: localhost
database_name: ''
database_pass: ''
database_user: ''
...
Reconfig, just to make sure -- the region controller seems to start fine:
root@spoink:~# dpkg-reconfigure -fnoninteractive maas-region-
* Stopping web server apache2
*
maas-regiond stop/waiting
maas-regiond start/running
* Restarting web server apache2
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
...done.
maas-clusterd stop/waiting
maas-clusterd start/running, process 17899
But it's not actually functional:
root@spoink:~# maas-region-admin createadmin --username=
Traceback (most recent call last):
File "/usr/sbin/
main()
File "/usr/sbin/
run()
File "/usr/sbin/
management.
File "/usr/lib/
utility.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
output = self.handle(*args, **options)
File "/usr/lib/
username, email=email, password=password)
File "/usr/lib/
**extra_fields)
File "/usr/lib/
user.
File "/usr/lib/
force_
File "/usr/lib/
with transaction.
File "/usr/lib/
if connection.
File "/usr/lib/
self.
File "/usr/lib/
self.connect()
File "/usr/lib/
conn_params = self.get_
File "/usr/lib/
"settings.
django.
Update: maas 1.9.0+bzr4533-
description: | updated |
Changed in maas: | |
milestone: | 1.9.1 → 1.9.2 |
Changed in maas: | |
milestone: | 1.9.2 → 1.9.3 |
Changed in maas: | |
milestone: | 1.9.3 → 1.9.4 |
Changed in maas: | |
milestone: | 1.9.4 → 1.9.5 |
HI Peter,
I've tried to reproduce this over and over, but I've been unable to reproduce it. I have two questions:
1. When you purged MAAS, did you answer Yes to all questions asked about purging the DB?
2. Can you reproduce this consistently?
Marking this incomplete as I can't seem to reproduce it in various environments.