Periodic Recovery attempts to create ERROR'd secondary zones

Bug #1563904 reported by Tim Simmons
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

If you've got a secondary zone that failed to zone transfer, it goes to ERROR.

Then, when it's in ERROR-CREATE state, periodic recovery will come along and try to recover it. This is not ideal because recovery doesn't know about secondary zones, and ends up trying to create it, which will fail because the zone has no NS records.

As an example, with a BIND backend:

1. Create a secondary zone, with bogus masters/etc
2. The zone will go to error
3. Wait until the Periodic Recovery runs
4. You will see that the process attempts to create the zone. Which, in BIND will fail, because there are no NS records.

It will do this forever.

This is a bit sticky, but we could probably start by making recovery not create ERROR'd secondary zones. Although, at some point, you'd want that to to get created, and it could be a complete zone, but still be in ERROR.

This could be an argument for a "Terminal" ERROR state, something that Designate can ignore, except in very specific cases (like a secondary zone that's broken?). Or just more ERROR states in general.

Tim Simmons (timsim)
description: updated
Tim Simmons (timsim)
Changed in designate:
importance: Undecided → High
milestone: none → newton-1
assignee: nobody → Tim Simmons (timsim)
status: New → Triaged
Changed in designate:
milestone: newton-1 → newton-2
Changed in designate:
milestone: newton-2 → none
Changed in designate:
assignee: Tim Simmons (timsim) → nobody
tomas cribb (tomascribb)
Changed in designate:
status: Triaged → Fix Committed
status: Fix Committed → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.