yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/rocky
   Importance: Undecided
       Status: New

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova/rocky
   Importance: Undecided => Medium

** Changed in: nova/queens
   Importance: Undecided => Medium

** Changed in: nova/queens
       Status: New => In Progress

** Changed in: nova/rocky
       Status: New => In Progress

** Changed in: nova/queens
     Assignee: (unassigned) => Hang Yang (hangyang)

** Changed in: nova/rocky
     Assignee: (unassigned) => Hang Yang (hangyang)

-- 
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) queens series:
  In Progress
Status in OpenStack Compute (nova) rocky series:
  In Progress

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