Detaching pre-existing port fails to remove user's dns record
Bug #1812110 reported by
Hang Yang
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Hang Yang | ||
Pike |
Confirmed
|
Medium
|
Unassigned | ||
Queens |
Fix Committed
|
Medium
|
Hang Yang | ||
Rocky |
Fix Committed
|
Medium
|
Hang Yang |
Bug Description
Environment:
Queens: Nova, Neutron, Designate(External DNS)
Network has dns_domain set
Steps to reproduce:
1. Create a port from the network
2. Create an instance with the port attached, dns_name in the port will be updated and a record will be created in user's recordset.
3. Delete the instance.
4. Check the port, the dns_name is reset to empty but the dns record under user's zone is not removed.
This also affects the usage of orchestration components like Senlin/Heat since they usually create a port separately and then create an instance with the port.
This bug was filed in Neutron before and has more debug information: https:/
Changed in nova: | |
assignee: | nobody → Hang Yang (hangyang) |
tags: | added: neutron |
Changed in nova: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/631684
Review: https:/