maas uninstallable on vivid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
maas (Ubuntu) |
Fix Released
|
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)
Changed in maas (Ubuntu): | |
importance: | Undecided → Critical |
tags: | added: juju-net |
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'