[2.0a1] dbconfig-common seems confused with maas

Bug #1553648 reported by Mark Shuttleworth on 2016-03-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Andres Rodriguez

Bug Description

When setting up the MAAS region controller package, I often see odd behaviour from dbconfig-common.

First, on install, it asks me if I want to use the local version of maas-region-controller.conf or overwrite with the maintainer version. Poking around doesn't actually show the maas-region-controller.conf being there at all, anyway. Regardless of what I say, the install script seems to proceed by installing the needed config, but I do see this:

Setting up maas-region-controller (2.0.0~alpha1+bzr4736-0ubuntu1~xenial2) ...
dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf
stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory

Related branches

Andres Rodriguez (andreserl) wrote :

I've have file [1] against dbconfig-common, provided we have not changed the usage of dbconfig recently. There might have been a regression introduce in dbconfig-common on the update made on 2016-02-22 .

[1]: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757

Changed in maas:
status: New → Confirmed
Andres Rodriguez (andreserl) wrote :

(we'll also investigate this for sure though).

Changed in maas:
status: Confirmed → Triaged
importance: Undecided → High
assignee: nobody → Andres Rodriguez (andreserl)
milestone: none → 2.0.0
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
status: Fix Released → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers