[2.0a1] dbconfig-common seems confused with maas
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
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-
Setting up maas-region-
dbconfig-common: writing config to /etc/dbconfig-
stat: cannot stat '/etc/dbconfig-
Related branches
- Mike Pontillo (community): Approve
-
Diff: 54 lines (+11/-11)2 files modifieddebian/changelog (+8/-6)
debian/maas-region-controller.postrm (+3/-5)
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 |
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