yahoo-eng-team team mailing list archive

[OpenStack Infra <1812110@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/631684
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b797f6f7e99fdef380340d6fe29e4004be48781
Submitter: Zuul
Branch:    master

commit 1b797f6f7e99fdef380340d6fe29e4004be48781
Author: Hang Yang <hangyang@xxxxxxxx>
Date:   Thu Jan 17 16:57:56 2019 -0800

    Fix port dns_name reset
    
    When external DNS service is enabled, use user's context to request
    dns_name reset instead of using admin context. The dns record need
    be found in user's zone and recordset.
    
    Change-Id: I35335b501f8961b9ac8e5f92e0686e402b78617b
    Closes-Bug: #1812110


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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

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