Provide a mechanism to populate domains in new pdns4 nodes

Bug #1867011 reported by Andrew Bogott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
New
Undecided
Unassigned

Bug Description

Running with designate Pike and pdns4:

I was recently required to reimage and rebuild one of my designate/pdns4 nodes. With the new pdns4 drivers there's no way to actively force a domain sync between designate and pdns, which meant that domains only appeared gradually as user accessed them.

Ultimately I wrote a script that enumerated every domain, created a recordset and then deleted it. That populated the domains in the new node; before running that script pdns was in an ugly split-brain state.

It's possible I'm misunderstanding how this is supposed to work, or this is fixed in a newer release. If not, we really need either an explicit way to force that sync (probably via a nova-manage command) or add some kind of polling behavior to designate to notice missing domains.

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.