Activity log for bug #1710308

Date Who What changed Old value New value Message
2017-08-11 23:46:36 Mike Pontillo bug added bug
2017-08-11 23:47:15 Mike Pontillo nominated for series maas/2.2
2017-08-11 23:47:15 Mike Pontillo bug task added maas/2.2
2017-08-11 23:47:20 Mike Pontillo maas/2.2: status New Triaged
2017-08-11 23:47:21 Mike Pontillo maas/2.2: importance Undecided High
2017-08-11 23:47:26 Mike Pontillo maas/2.2: milestone 2.2.3
2017-08-12 00:09:15 Mike Pontillo maas: importance High Critical
2017-08-12 00:09:17 Mike Pontillo maas/2.2: importance High Critical
2017-08-14 15:32:04 Robie Basak bug added subscriber Robie Basak
2017-08-18 14:43:27 Blake Rouse maas: status Triaged In Progress
2017-08-18 14:43:28 Blake Rouse maas: assignee Blake Rouse (blake-rouse)
2017-08-18 14:44:50 Blake Rouse merge proposal linked https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/329260
2017-08-18 15:11:51 Felipe Reyes bug added subscriber Felipe Reyes
2017-08-19 01:00:00 MAAS Lander maas: status In Progress Fix Committed
2017-08-19 20:41:32 Dominique Poulain bug added subscriber Dominique Poulain
2017-08-21 17:03:27 Andres Rodriguez maas: milestone 2.3.0 2.3.0alpha2
2017-08-21 21:33:25 Mike Pontillo summary [2.2] MAAS should throttle bind reloads [2.2] MAAS should confirm the success of DNS reloads by checking the zone serial
2017-08-21 21:34:47 Mike Pontillo description MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.) MAAS should: - Throttle consecutive updates. (For example, when the first DNS change occurs, schedule a task for a few seconds in the future which will update DNS, and don't ever schedule more additional updates while that task is pending.) - Wait for confirmation that the reload is complete before starting another update. MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.) MAAS should wait for confirmation that the reload is complete before starting another update.
2017-08-21 21:35:25 Mike Pontillo description MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.) MAAS should wait for confirmation that the reload is complete before starting another update. MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.) MAAS should wait for confirmation that the reload is complete before starting another update. See also: bug #1712205.
2017-08-21 21:38:31 Mike Pontillo description MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.) MAAS should wait for confirmation that the reload is complete before starting another update. See also: bug #1712205. MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.) MAAS should wait for confirmation that the reload is complete before starting another update. See also: bug #1712205 (throttling of DNS reload requests) and bug #1710310 (better service monitoring, separate from the reload confirmation itself).
2017-08-22 13:32:33 Launchpad Janitor merge proposal linked https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/329366
2017-08-22 13:33:18 Blake Rouse maas/2.2: status Triaged In Progress
2017-08-22 15:55:15 MAAS Lander maas/2.2: status In Progress Fix Committed
2017-08-22 18:11:39 Andres Rodriguez maas: status Fix Committed Fix Released
2018-03-27 18:47:35 Andres Rodriguez maas/2.2: status Fix Committed Fix Released