** Changed in: nova/queens Assignee: Matt Riedemann (mriedem) => Hang Yang (hangyang)
** Also affects: nova/pike Importance: Undecided Status: New ** Changed in: nova/pike Status: New => Confirmed ** Changed in: nova/pike Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1812110 Title: Detaching pre-existing port fails to remove user's dns record Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: Confirmed Status in OpenStack Compute (nova) queens series: In Progress Status in OpenStack Compute (nova) rocky series: Fix Committed 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://bugs.launchpad.net/neutron/+bug/1741079 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1812110/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp