[2.2] MAAS should confirm the success of DNS reloads by checking the zone serial

Bug #1710308 reported by Mike Pontillo on 2017-08-11
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
Blake Rouse
2.2
Critical
Unassigned

Bug 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 (throttling of DNS reload requests) and bug #1710310 (better service monitoring, separate from the reload confirmation itself).

Related branches

Changed in maas:
importance: High → Critical
Robie Basak (racb) wrote :

You might find the logic of the "watershed" CLI tool useful. Wrapping the "rndc reload" call with the watershed command might also work around the underlying reload hanging issue. It's in the chiark-utils-bin package.

Changed in maas:
status: Triaged → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 2.3.0 → 2.3.0alpha2
summary: - [2.2] MAAS should throttle bind reloads
+ [2.2] MAAS should confirm the success of DNS reloads by checking the
+ zone serial
description: updated
description: updated
description: updated
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers