Comment 25 for bug 1902425

I've just bumped into the same issue with snapped 2.9.2 (9164-g.ac176b5c4).

I seem to have been hitting this issue when repeatedly redeploying a machine, though I can't say for certain if this is a trigger for this behaviour. In this state, the machine can be deployed without issue but its name cannot be resolved via MAAS' DNS.

My workaround was to redeploy with a static address (the same address in this case), then release and set addressing back to auto-assign. Everything then went back to normal.

I've attached the past few days of regiond logging, but note that I've not explicitly tested/triggered this to reproduce the problem; all of the above was just in passing.

The activity with host clatter-deceased on the 2021-03-22 in the attached regiond.log covers the above.