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
Bug #1553757 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbconfig-common (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ucf (Debian) |
Fix Released
|
Unknown
|
|||
ucf (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In MAAS, we make use of dbconfig common. We have been using it exactly the same way for awhile now and we have just starting seeing the following on install or upgrade:
dbconfig-common: writing config to /etc/dbconfig-
stat: cannot stat '/etc/dbconfig-
Also, before this it always asks whether to use the local version of the file or install a new one in case of an upgrade.
Changed in ucf (Debian): | |
status: | Unknown → Fix Released |
Changed in ucf (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
Hi Andres,
On 06-03-16 17:42, Andres Rodriguez wrote: common/ maas-region- controller. conf
> In MAAS, we make use of dbconfig common. We have been using it exactly
> the same way for awhile now and we have just starting seeing the
> following on install or upgrade:
>
> dbconfig-common: writing config to /etc/dbconfig-
dbconfig-common has always done that. So nothing new.
> stat: cannot stat '/etc/dbconfig- common/ maas-region- controller. conf': No such file or directory
Any idea why this happens? What is special about your setup? How did you common directory controller. conf file missing? Is this on
configure dbconfig-common? Is the /etc/dbconfig-
missing, or is the maas-region-
BOTH install and upgrade or only during install or only during upgrade?
> Also, before this it always asks whether to use the local version of the
> file or install a new one in case of an upgrade.
I am not 100% sure if I understand what you mean. The behavior that you
describe seems to be the question raised by ucf. Are you now saying that
that is not happening anymore? That would indeed be a serious bug, but
nothing on that front has changed. The only thing that I can think of on
this front is that I removed the date of installation, such that ucf
will not ask the question if the content of the file has not changed.
Can you confirm that this is what you mean?
Furthermore, there is important information missing: about which version
of dbconfig-common are you talking? With which version did you
experience the alleged change?
Paul