mDNS fails to handle SOA etc queries correctly when multiple pools have a RRSet of the same name and type

Bug #1616541 reported by Kiall Mac Innes on 2016-08-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Critical
Unassigned

Bug Description

In https://github.com/openstack/designate/blob/4bc65992ce98e1146803ec6befdb87315bd61b1b/designate/mdns/handler.py#L342

When 2 recordsets in different pools share a name and type, then L365 will raise a NotFound (not enough info was provided to select exactly 1 recordset). This will prevent both zones from zone transferring, as the SOA query would blow up.

Tim Simmons (timsim) on 2016-08-31
Changed in designate:
status: New → Triaged
importance: Undecided → High
milestone: none → rc1
importance: High → Critical
Changed in designate:
milestone: rc1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers