group.of.nepali.translators team mailing list archive

[Blake Rouse <blake.rouse@xxxxxxxxxxxxx>]

** Changed in: maas (Ubuntu Bionic)
       Status: Confirmed => In Progress

** Changed in: maas (Ubuntu Bionic)
     Assignee: (unassigned) => Blake Rouse (blake-rouse)

** Also affects: maas/2.4
   Importance: Undecided
       Status: New

** Changed in: maas/2.4
       Status: New => Fix Committed

** Changed in: maas/2.4
    Milestone: None => 2.4.3

** Changed in: maas/2.4
     Assignee: (unassigned) => Blake Rouse (blake-rouse)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1710278

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

Status in BIND:
  New
Status in MAAS:
  Fix Committed
Status in MAAS 2.2 series:
  Fix Released
Status in MAAS 2.4 series:
  Fix Committed
Status in MAAS 2.6 series:
  Fix Released
Status in MAAS 2.7 series:
  Fix Committed
Status in bind9 package in Ubuntu:
  In Progress
Status in maas package in Ubuntu:
  Confirmed
Status in bind9 source package in Xenial:
  In Progress
Status in bind9 source package in Bionic:
  In Progress
Status in maas source package in Bionic:
  In Progress
Status in bind9 source package in Disco:
  In Progress
Status in bind9 source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * systemd thinks the service is running, but it does not respond to
  any commands or requests. Also, it doesn't respond to signals other
  than kill -9. service restarts hang, rndc hangs.

   * being that the deadlock is in bind9 that ships in bionic the issue
  needs to be backported to 2.4.3 so MAAS from the archive in bionic can
  handle the deadlock and get bind9 unstuck.

   * change in MAAS watches for this case to occur with bind9, then MAAS
  will force kill the service and restart it.

  [Test Case]

   * very hard to reproduce but the issue occurs when bind9 deadlocks,
  it response to nothing over the network or rndc. SIGTERM does not kill
  it only SIGKILL works to force kill the process and get systemd to
  restart it.

  
  [Regression Potential] 

   * possible that bind9 will not be started correctly or possible that
  bind9 will be placed into a forever restart loop

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