Hi Mark,

Still seeing it with 18.04 and 2.6.  The sweet spot seems to be when
MAAS is receiving lots of DNS requests while simultaneously doing DNS
reloads (as you alluded to in this case).

I'm attempting to setup a simplified repro scenario which basically will
do this:

1) enlist 50+ new machines on a untagged subnet *with DNS left blank* forcing 
nodes to DNS query MAAS
2) Leave machines PXE interface with Autoassign IP (so every deploy/releaes 
forces a DNS reload)
3) deploy and release (repeat until error)

will report back with findings.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710278

Title:
  [2.3a1] named stuck on reload, DNS broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to