MAAS randomly doesn't generate zone files on restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Low
|
Unassigned |
Bug Description
MAAS installed by snap. Happens the same with both 3.4.0 and 3.4.1 (rev 34087).
If it fails to generate the zone files (including reverse DNS), here's all from /var/snap/
bind.keys
cache
db.0
db.127
db.255
db.empty
db.local
keys.conf.maas
named.conf
named.conf.
named.conf.local
named.conf.maas
named.conf.options
named.conf.
named.conf.
rndc.conf.maas
zones.rfc1918
Obviously, named service complains about files not being found:
18-Mar-2024 21:37:51.189 zone 116.31.
18-Mar-2024 21:37:51.189 zone 7.45.10.
18-Mar-2024 21:37:51.189 zone 9.74.10.
18-Mar-2024 21:37:51.189 zone 2.45.10.
18-Mar-2024 21:37:51.189 zone 6.45.10.
18-Mar-2024 21:37:51.189 zone 15.1.16.
18-Mar-2024 21:37:51.189 zone 3.45.10.
18-Mar-2024 21:37:51.189 zone 5.45.10.
Also happens to "maas" zone and any other custom zones defined.
Steps to reproduce:
- scenario 1 - snap refreshed automatically and restarted.
- scenario 2 - MAAS goes through a backup process as described here: https:/
snap stop maas
snap save maas
snap export-snapshot
snap forget
snap restart maas
Temporary workarounds:
- scenario 1 - stop automatic refresh (snap refresh --hold=forever)
- scenario 2 - after last "snap restart maas", verify custom zone file present and if it's missing, restart maas again.
Problem usually fixed by "snap restart maas".
Changed in maas: | |
status: | Incomplete → New |
Hi there, can you please provide a sos-report from when this occurs?