maas uninstallable on vivid

Bug #1430025 reported by Scott Moser
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Undecided
Unassigned
maas (Ubuntu)
Fix Released
Critical
Unassigned
Nominated for Vivid by Alberto Salvia Novella

Bug Description

sudo apt-get update -q
sudo apt-get install -qy maas maas-dhcp maas-dns

 ┌──────────────────────┤ Configuring maas-region-controller ├───────────────────────┐

 │ 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/postgresql/.s.PGSQL.5432"? │
 │ │
 │ 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-0ubuntu1
ProcVersionSignature: User Name 3.19.0-7.7-generic 3.19.0
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
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
PackageArchitecture: all
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Scott Moser (smoser) wrote :
Changed in maas (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Andres Rodriguez (andreserl) wrote :

I hit a different problem:

verifying database maasdb exists: success.
dbconfig-common: flushing administrative password
System check identified some issues:

WARNINGS:
?: (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://docs.djangoproject.com/en/dev/releases/1.6/#new-test-runner for more information.
Syncing...
Traceback (most recent call last):
  File "/usr/sbin/maas-region-admin", line 16, in <module>
    management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 533, in handle
    return self.handle_noargs(**options)
  File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 82, in handle_noargs
    old_app_store, cache.app_store = cache.app_store, SortedDict([
AttributeError: 'Apps' object has no attribute 'app_store'

Revision history for this message
Raphaël Badin (rvb) wrote :

@Andres, the crash you're seeing is bug 1430324.

Changed in maas (Ubuntu):
status: New → Confirmed
Revision history for this message
Raphaël Badin (rvb) wrote :

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-516c7ee2-8cb6-4c1f-b950-6b6900d74ead
● postgresql.service - PostgreSQL RDBMS
   Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
   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-516c7ee2-8cb6-4c1f-b950-6b6900d74ead systemd[1]: Starting PostgreSQL RDBMS...
Mar 10 13:03:49 server-516c7ee2-8cb6-4c1f-b950-6b6900d74ead systemd[1]: Started PostgreSQL RDBMS.

$ 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.

Revision history for this message
Raphaël Badin (rvb) wrote :

Couldn't this be bug 1424509? (Because after installing `postgresql` on vivid, the main cluster is down, see http://paste.ubuntu.com/10579015/)

Revision history for this message
Scott Moser (smoser) wrote :

Raphael, its quite possible you're right.

Revision history for this message
Martin Pitt (pitti) wrote :

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://launchpad.net/ubuntu/+source/postgresql-common/166bzr2 (stuck in proposed for a while, but should migrate in a few minutes now), which also caused postgresql@9.4-xxxx.service to not start up, while the "umbrella" postgresql.service was running (but that's just a no-op, and mostly just a dependency target).

Can you please re-try with the current vivid versions and with p-common 166bzr2?

Changed in maas (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Scott Moser (smoser) wrote :
Download full text (5.2 KiB)

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-0ubuntu1
  Version table:
     1.7.1+bzr3341-0ubuntu1 0
        500 http://nova.clouds.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

$ 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-common/maas-region-controller.conf

Creating config file /etc/dbconfig-common/maas-region-controller.conf with new version
creating postgres user maas: success.
verifying creation of user: success.
creating database maasdb: success.
verifying database maasdb exists: success.
dbconfig-common: flushing administrative password
System check identified some issues:

WARNINGS:
?: (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://docs.djangoproject.com/en/dev/releases/1.6/#new-test-runner for more information.
Syncing...
Traceback (most recent call last):
  File "/usr/sbin/maas-region-admin", line 16, in <module>
    management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 533, in handle
    return self.handle_noargs(**options)
  File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 82, in handle_noargs
    old_app_store, cache.app_store = cache.app_store, SortedDict([
AttributeError: 'Apps' object has no attribute 'app_store'
dpkg: error processing package maas-region-controller (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of maas:
 maas depends on maas-region-controller (= 1.7.1+bzr3341-0ubuntu1); however:
  Package maas-region-controller is not configured yet.

dpkg: error processing package maas (--configure):
 dependency problems - leaving unconfigured
Setting up maas-dns (1.7.1+bzr3341-0ubuntu1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
System check ide...

Read more...

Changed in maas (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Thanks Scott for confirming. Dropping this from my radar then :-)

Raphaël Badin (rvb)
tags: added: juju-net
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.