yahoo-eng-team team mailing list archive

[OpenStack Infra <1875981@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/728385
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=622714b63e08feaba4e81d218541319d2ffada30
Submitter: Zuul
Branch:    master

commit 622714b63e08feaba4e81d218541319d2ffada30
Author: Jens Harbott <j.harbott@xxxxxxxx>
Date:   Fri May 15 08:43:18 2020 +0000

    Optionally use admin powers when deleting DNS records
    
    This resolves a bug that causes stale records to be kept in place when
    an admin deletes a port, server or floating IP that was created in some
    project other than the admin project.
    
    Change-Id: I7cbb0e87a7e87f23ccf5d8750835b4785693473a
    Closes-Bug: #1875981


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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1875981

Title:
  Admin deleting servers or ports leaves orphaned DNS records

Status in neutron:
  Fix Released

Bug description:
  lets say we have a tenant user_side with zone example.com (dns_domain
  defined on a shared neutron network)

  so the user create a server (dns neutron extension enabled) which
  result a designate recordset below

  server1.example.com in zone example.com that only exist in the tenant
  user_side

  
  if an admin wants to delete server1 from the tenant user_side it will use 

  openstack server delete server1

  which will delete the server but will not delete the designate recordset since the zone example.com 
  does not exist in admin tenant

  
  which will leave an orphan record in designate

  the admin should be able to delete all the resources of server1
  including the designate recordset

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1875981/+subscriptions