Hi Andres,

On 07-03-16 06:07, Andres Rodriguez wrote:
> Sorry for not being clear enough.

NP, as long as you follow up on questions that is ok.

> The actual issue/concern I have is:
> 
> stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No
> such file or directory

Ack. I have a belly feeling that this may be related to the
implementation in ucf of Debian wish list bug 812321¹. Can you try once
again after you "touch /etc/dbconfig-common/maas-region-controller.conf".

> Now, the way I'm reproducing this issue right now is an install. I have
> remove/purged all the packages, include dbconfig common packages and
> made sure that /etc/dbconfig-common doesn't exist :

This looks like dbconfig-common isn't cleaning up properly on purge and
keeps the file registered with ucf. Weird, I'll try to investigate, but
I do purging a lot with all kind of example packages in my test suite²
and have never seen this before.

> The installation resumes, and It asks me the question to: http://pastebin.ubuntu.com/15319155/

Right. As expected, these are questions from ucf. So it may be that the
issue lies there.

> Right after answering the questions (no matter if I say install the
> package maintainer's version  or  keep the local version currently
> installed) , it is always the same result:
> 
> 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

That at least is a bug in ucf. When you answer to use the package
maintainers version, it must create the file as requested. So I guess we
could at least file an additional bug against ucf. But let's wait until
we find out if there isn't just one issue here.

> As you can see, the file doesn't get created. Now, what I'm really
> wondering if is there is only an issue in systems where dbconfig-common
> was first upgraded to the latest version  (2.0.3), and not on a freshly
> installed system where dbconfig-common is latest, as I've not been able
> to reproduce this on a freshly installed system yet.

As said, I suspect this may be because the file is still registered with
ucf. During install (after purge or on a clean system) ucf should not
need to ask the question. It only should do that when there once was
already a file (either still is or ucf knows that the admin has deleted
the file).

> Now, to answer your last question, the question raised by UCF was never there because we preseed the following:
> 
> set_question maas-region-controller/dbconfig-install true

Doesn't look related. But how ugly is this, anyways. This means that you
are preventing an admin from defering the setup to later, e.g. because
she doesn't have the admin rights on the database he wants to use. By
the way, you do know that when an admin installs dbconfig-no-thanks,
dbconfig-common will not run, irrespective of your preseeding.

> Or maybe, the preseeding doesn't really matter and we just have never
> gotten into a similar situation, hence it never really has been shown
> before.

As said, this may be related to an updated ucf. I'll try to reproduce.

Paul

¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812321
² https://ci.debian.net/packages/d/dbconfig-common/unstable/amd64/ (test
log; test case install-examples)