After short investigation we've clarified a following: bug is reproducible when another NS recordset is exists in the zone (if no any NSs - no problems with NS Pool update)
and, as seen from IRC:
<Kiall> ekarlso has tracked it down to a bug in Designate caused by the second NS RRSet in the zone
<Kiall> That's clearly not a case we've tested before
After short investigation we've clarified a following: bug is reproducible when another NS recordset is exists in the zone (if no any NSs - no problems with NS Pool update)
and, as seen from IRC:
<Kiall> ekarlso has tracked it down to a bug in Designate caused by the second NS RRSet in the zone
<Kiall> That's clearly not a case we've tested before
DB dump (where bug is reproducible): http:// paste.openstack .org/show/ jv40EYNiwblMY6W 1tkrd/ paste.openstack .org/show/ urwbpEDZg3ETvDT 4GnFe/
Query with error: http://