Invalid MX record during recordset create/update cause ZONE to enter in Error state

Bug #1927304 reported by kiran pawar
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Designate
Fix Released
Undecided
Unassigned

Bug Description

In Designate it is not possible to create an MX (Mail) record without a . (dot) at the end of fqdn. Which is the way it should be per RFC.
However, Designate allows users to update the MX record and omit/remove the . (dot) at the end of fqdn.

Case 1)
openstack recordset create --record "20 xxxx.test.com" --type MX zone_id mail2.test.com.

Case 2)
openstack recordset create --record "20 xxxx.test.com." --type MX zone_id mail2.test.com.
openstack recordset set --record "20 xxxx.test.com" --type MX zone_id recordset_id

In either of case 1 or 2, causes the zone to be stuck in PENDING and go to ERROR at some point, because the backend server (Bind) cannot fetch the zone from Designate-mdns.

kiran pawar (kpdev)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/designate/+/790000

Changed in designate:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to designate (master)

Reviewed: https://review.opendev.org/c/openstack/designate/+/790000
Committed: https://opendev.org/openstack/designate/commit/536315e38ccc06193d9f8b83770aab8f671f6fa8
Submitter: "Zuul (22348)"
Branch: master

commit 536315e38ccc06193d9f8b83770aab8f671f6fa8
Author: kpdev <email address hidden>
Date: Thu May 6 06:56:11 2021 +0200

    Validate MX records during recordset create or update

    If invalid MX record is provided during recordset create command or
    valid record is updated to invalid record using recordset set command,
    causes recordset creation/updation failure. This leads to zone enter
    in ERROR state and all further recordset creation calls fail. Validate
    the records within recordset during create or update call.

    Closes-Bug: #1927304
    Change-Id: I0ace4d6c4ad6a6ee236e3af23805b01345d60a42

Changed in designate:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/designate 15.0.0.0rc1

This issue was fixed in the openstack/designate 15.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (stable/yoga)

Fix proposed to branch: stable/yoga
Review: https://review.opendev.org/c/openstack/designate/+/877164

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to designate (stable/yoga)

Reviewed: https://review.opendev.org/c/openstack/designate/+/877164
Committed: https://opendev.org/openstack/designate/commit/86a8cc5f525f6e2ab5e287c027b3bd18b9fbfbd3
Submitter: "Zuul (22348)"
Branch: stable/yoga

commit 86a8cc5f525f6e2ab5e287c027b3bd18b9fbfbd3
Author: kpdev <email address hidden>
Date: Thu May 6 06:56:11 2021 +0200

    Validate MX records during recordset create or update

    If invalid MX record is provided during recordset create command or
    valid record is updated to invalid record using recordset set command,
    causes recordset creation/updation failure. This leads to zone enter
    in ERROR state and all further recordset creation calls fail. Validate
    the records within recordset during create or update call.

    Closes-Bug: #1927304
    Change-Id: I0ace4d6c4ad6a6ee236e3af23805b01345d60a42

tags: added: in-stable-yoga
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/designate 14.0.2

This issue was fixed in the openstack/designate 14.0.2 release.

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.