I can reproduce this and I think the error is in the neutron code, not in designate.
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Status: New => Confirmed -- 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 for other tenants Status in Designate: New Status in neutron: Confirmed 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/designate/+bug/1875981/+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