Neutron doesn't delete Designate entry when port is deleted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
When a port with a FIP and DNS association is deleted, Neutron integration is not deleting the DNS entry from Designate.
To reproduce use the following flow:
# Create a Designate zone and associate with a tenant network
openstack zone create --email <email address hidden> example.org.
neutron net-create net1 --dns-domain example.org.
neutron subnet-create --name sub1 net1 192.168.1.0/24
# Create a router, and attach tenant network to a public network
neutron router-create rtr
neutron router-
neutron router-
neutron router-gateway-set rtr public
# Create a port, associate with a FIP
PORT_ID=$(neutron port-create --name testport --dns-name testport net1 | awk '/ id /{print $4}')
neutron floatingip-create --port-id $PORT_ID public
# Entry should be seen in Designate recordset
openstack recordset list example.org.
# Delete port
neutron port-delete $PORT_ID
# Entry is expected to be deleted from Designate recordset. Yet it isn't
openstack recordset list example.org.
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: designate dns |
Changed in neutron: | |
assignee: | nobody → Miguel Lavalle (minsel) |
Changed in neutron: | |
assignee: | Miguel Lavalle (minsel) → Salvatore Orlando (salvatore-orlando) |
tags: | added: neutron-proactive-backport-potential |
@Miguel: Are you actively working on this? Otherwise maybe better unassign yourself?