named.conf.maas tries to include conf files from an unexisting version

Users
1

After a fresh install using 3.7 edge from a snap install, I end up having named restarting itself constantly. Reason is the first line in the configuration file:
include “/var/snap/maas/40405/bind/named.conf.rndc.maas”;

I only have folders 40431, 40441, common and current->40441 present under /var/snap/maas.

How did I end up in this situation? And how do I solve it?

2

Did you have maas installed on this host before? Did you just sudo snap remove maas or did you sudo snap remove --purge maas?

3

No, this is my first install. I’ve been uninstalling with purge before just to get everything removed, but I’ve encountered lots and lots of problems with 3.7 or 3.7/edge. So this setup is purely from scratch so that I’m 100% sure I don’t have any leftovers.

4

Oh and it’s installed by Ansible with a play like this (don’t mind the formatting, I won’t struggle for 15min just to get that right)

name: Install MAAS
community.general.snap:
name: maas
channel: “{{ maas_version }}”

5

I think you missed the --purge flag at some point in the past.

what’s the output of snap saved maas?

6

Uhm maybe you have multiple directories because 3.7/edge got some updates and the snap self-upgraded

7

But that shouldn’t matter since this is a clean install on a VM that’s been built from scratch up. This ubuntu VM never had MAAS previously installed to begin with. But I do see your point. It looks exactly like that would have happend. Anyway, how do I fix this since those folders are read-only aren’t they, with snap and all?

8

Yes, as I pointed out earlier. I do have
40431
40441
common
current->40441

or actually, since yesterday that got changed. Now it’s
40441
40446
common
current → 40446

If I look the content of the file under 40446:

root@maas02:~# cat /var/snap/maas/40446/bind/named.conf.maas
include “/var/snap/maas/40405/bind/named.conf.rndc.maas”;
include “/var/snap/maas/40405/bind/keys.conf.maas”;
…

Is MAAS still running the instance that got launched when 40405 WAS “current”, and it keeps rewriting the content of named.conf.maas as if 40405 still was “current”?

9

Ah, forgot to mention that I don’t have any snapshots. i.e. “No snapshots found.”