maas uninstallable on vivid
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | MAAS |
Undecided
|
Unassigned | ||
| | maas (Ubuntu) |
Critical
|
Unassigned | ||
Bug Description
sudo apt-get update -q
sudo apt-get install -qy maas maas-dhcp maas-dns
┌─────
│ An error occurred while installing the database: │
│ │
│ psql: could not connect to server: No such file or directory Is the server │
│ running locally and accepting connections on Unix domain socket │
│ "/var/run/
│ │
│ If at this point you choose "retry", you will be prompted with all the │
│ configuration questions once more and another attempt will be made at performing │
│ the operation. "retry (skip questions)" will immediately attempt the operation │
│ again, skipping all questions. If you choose "abort", the operation will fail │
│ and you will need to downgrade, reinstall, reconfigure this package, or │
│ otherwise manually intervene to continue using it. If you choose "ignore", the │
│ operation will continue, ignoring further errors from dbconfig-common.
..
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: maas 1.7.1+bzr3341-
ProcVersionSign
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
Date: Mon Mar 9 21:12:23 2015
Ec2AMI: ami-00000201
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
PackageArchitec
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)
| Scott Moser (smoser) wrote : | #1 |
| Changed in maas (Ubuntu): | |
| importance: | Undecided → Critical |
| Andres Rodriguez (andreserl) wrote : | #2 |
| Raphaël Badin (rvb) wrote : | #3 |
@Andres, the crash you're seeing is bug 1430324.
| Changed in maas (Ubuntu): | |
| status: | New → Confirmed |
| Raphaël Badin (rvb) wrote : | #4 |
I get the same crash (as described on the bug) when I installing 1.7 on Vivid. It seems the DB is down:
$ sudo service postgresql status
sudo: unable to resolve host server-
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/
Active: active (exited) since Tue 2015-03-10 13:03:49 UTC; 13min ago
Process: 16884 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 16884 (code=exited, status=0/SUCCESS)
Mar 10 13:03:49 server-
Mar 10 13:03:49 server-
$ ps aux | grep postgr -> nothing
Did something in postgresql's packaging change drastically with the vivid release? My guess is that this is all related to the switch to systemd.
| Raphaël Badin (rvb) wrote : | #5 |
Couldn't this be bug 1424509? (Because after installing `postgresql` on vivid, the main cluster is down, see http://
| Scott Moser (smoser) wrote : | #6 |
Raphael, its quite possible you're right.
| Martin Pitt (pitti) wrote : | #7 |
This sounds like bug 1429734. That effect on PostgreSQL was that after apt-get install postgresql-9.4 the cluster wasn't running if your system was in "degraded" mode, i. e. you had at least one failed unit. This was fixed yesterday.
Another possibility was the race condition fixed in https:/
Can you please re-try with the current vivid versions and with p-common 166bzr2?
| Changed in maas (Ubuntu): | |
| status: | Confirmed → Incomplete |
| Scott Moser (smoser) wrote : | #8 |
I think we're down to the maas issue that Raphael described now.
Postgres is fixed (I marked bug 1427950 fix-released).
See full log attached, but here is what I see now.
$ apt-cache policy maas
maas:
Installed: (none)
Candidate: 1.7.1+bzr3341-
Version table:
1.
500 http://
$ sudo apt-get install -qy maas
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
apache2 apache2-bin apache2-data apache2-utils authbind bind9 bind9utils
...
dbconfig-common: writing config to /etc/dbconfig-
Creating config file /etc/dbconfig-
creating postgres user maas: success.
verifying creation of user: success.
creating database maasdb: success.
verifying database maasdb exists: success.
dbconfig-common: flushing administrative password
[31;1mSystem check identified some issues:
WARNINGS:
[33;1m?: (1_6.W001) Some project unittests may not execute as expected.
HINT: Django 1.6 introduced a new default test runner. It looks like this project was generated using Django 1.5 or earlier. You should ensure your tests are all running & behaving as expected. See https:/
[0mSyncing...
Traceback (most recent call last):
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/
return self.handle_
File "/usr/lib/
old_app_store, cache.app_store = cache.app_store, SortedDict([
AttributeError: 'Apps' object has no attribute 'app_store'
dpkg: error processing package maas-region-
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of maas:
maas depends on maas-region-
Package maas-region-
dpkg: error processing package maas (--configure):
dependency problems - leaving unconfigured
Setting up maas-dns (1.7.1+
No apport report written because the error message indicates its a followup error from a previous failure.
[31;1mSystem check ide...
| Changed in maas (Ubuntu): | |
| status: | Incomplete → Confirmed |
| Scott Moser (smoser) wrote : | #9 |
| Martin Pitt (pitti) wrote : | #10 |
Thanks Scott for confirming. Dropping this from my radar then :-)
| tags: | added: juju-net |
If this bug is fixed, please set its importance accordingly.
| Changed in maas: | |
| status: | New → Confirmed |
| Changed in maas (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in maas (Ubuntu): | |
| status: | Triaged → Fix Released |
| Changed in maas: | |
| status: | Confirmed → Fix Released |


I hit a different problem:
verifying database maasdb exists: success.
dbconfig-common: flushing administrative password
System check identified some issues:
WARNINGS: /docs.djangopro ject.com/ en/dev/ releases/ 1.6/#new- test-runner for more information. maas-region- admin", line 16, in <module> execute_ from_command_ line() python2. 7/dist- packages/ django/ core/management /__init_ _.py", line 385, in execute_ from_command_ line execute( ) python2. 7/dist- packages/ django/ core/management /__init_ _.py", line 377, in execute fetch_command( subcommand) .run_from_ argv(self. argv) python2. 7/dist- packages/ django/ core/management /base.py" , line 288, in run_from_argv execute( *args, **options.__dict__) python2. 7/dist- packages/ django/ core/management /base.py" , line 338, in execute python2. 7/dist- packages/ django/ core/management /base.py" , line 533, in handle noargs( **options) python2. 7/dist- packages/ south/managemen t/commands/ syncdb. py", line 82, in handle_noargs
?: (1_6.W001) Some project unittests may not execute as expected.
HINT: Django 1.6 introduced a new default test runner. It looks like this project was generated using Django 1.5 or earlier. You should ensure your tests are all running & behaving as expected. See https:/
Syncing...
Traceback (most recent call last):
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/
return self.handle_
File "/usr/lib/
old_app_store, cache.app_store = cache.app_store, SortedDict([
AttributeError: 'Apps' object has no attribute 'app_store'