Comment 10 for bug 1553757

Hi Paul,

So this is what I did:

1. Modified the postrm to not check for
/etc/dbconfig-common/maas-region-controller.conf
2. purged maas
3. re-installed maas and the result was:
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

The, I did:
1. Install maas with buggy postrm.
2. purged maas. / dbconfig*, /etc/dbconfig-common was left with
maas-region-controller.postinst, so I removed it.
3. Installed maas again, and the result:
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
4. purged maas/dbconfig, but manually fixed maas' postrm.

Finally I did:
1. Installed maas, result:
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
2. purged maas/dbconfig* with fixed postrm. /etc/dbconfig-common got
removed.
4. Installed maas again, and things went well.

So this confirms that because of the postrm bug, we would see the install
issues. So fixing this is MAAS definitely fixes the error I was having. I'm
gonna mark the bug invalid, however, I wonder if dbconfig-common should do
something to not to write a new config ?

On Tue, Mar 8, 2016 at 2:32 PM, Paul Gevers <email address hidden>
wrote:

> Hi Andres,
>
> On 08-03-16 04:41, Andres Rodriguez wrote:
> > Sorry for the delay and thanks for looking into it. Good catch on the
> > postrm. At least I know that's my fault. That being said, I wonder if
> > unregistering the file actually explains why it doesn't get re-created.
>
> Hmm, I was a bit to certain in my phrasing. I should have said: it COULD
> be caused by the admin and the way maas handles purging. By no means did
> I mean that it is certain here.
>
> > The
> > funny thing here is that this is the first time it actually does
> something
> > similar (not creating the file), and the packaging hasn;'t really change
> in
> > that area.
>
> Neither has dbconfig-common.
>
> > I'm gonna try to reproduce what you suggest with touching the file and
> see
> > whether things get resolved with the fix to postrm..
>
> Good.
>
> By the way, I tried removing the configuration file while working with
> one of my example packages (included in the source of dbconfig-common)
> and the behavior of ucf is as expected.
>
> Unfortunately, on my Debian system I can't easily check installing maas
> with apt-get, as that is not available in Debian.
>
> Paul
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1553757
>
> Title:
> 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
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+subscriptions
>

--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer