Delete zone fails to propagate to all (Bind) nameservers in a pool depending on threshold_percentage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Critical
|
Ron Rickard |
Bug Description
Reproduction: I was testing this with two Bind servers in a single pool.
- In designate.conf, I set `threshold_
- I created a zone 'example.com.' through Designate's API and ensured that the zone propagated to both nameservers (i.e. that I could dig both nameservers successfully for that zone).
- I then killed only one Bind server (command line: `service bind9 stop`).
- I deleted the zone 'example.com.' through Designate's API. I saw that the zone was properly deleted from the only running Bind server.
- (At this point, getting the zone through the API correctly returns a 404. The zone was deleted on 1 of 2 nameservers, which is over the threshold_
- I restarted the Bind server I previously killed.
(At this point, I've sometimes seen the pool manager throw a DomainNotFound exception and sometimes not. Restarting the pool manager will produce the DomainNotFound exception. If I wait a bit, mini-dns seems to throw a DomainNotFound as well.)
In any case, this produces an inconsistency which is never resolved. One nameserver has deleted the zone, while the other nameserver never deletes the zone.
Additional info:
I notice this problem does not occur when setting `threshold_
description: | updated |
Changed in designate: | |
milestone: | none → kilo-2 |
assignee: | nobody → Ron Rickard (rjrjr) |
Changed in designate: | |
importance: | Undecided → Critical |
Changed in designate: | |
status: | Fix Committed → Fix Released |
Changed in designate: | |
milestone: | kilo-2 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/146246
Review: https:/