yahoo-eng-team team mailing list archive

["Dr. Jens Harbott" <1746627@xxxxxxxxxxxxxxxxxx>]

As I mentioned in the patch, combining neutron dns-integration with the
designate PTR functionality is not supported, so if this is the issue,
the bug is invalid. I actually think that we should deprecate and drop
the designate support for that in order to avoid such conflicts.

** Changed in: neutron
       Status: New => Invalid

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

Title:
  Reverse floating IP records are not removed when floating IP is
  deleted

Status in Designate:
  Triaged
Status in neutron:
  Invalid

Bug description:
  When I release/delete a floating IP from my project that has a
  corresponding FloatingIP PTR record the record is not deleted.

  Steps to reproduce:

  Assign a floating IP to my project
  Set a PTR record on my floating IP using the reverse floating IP API
  Release floatingIP

  PTR record still exists in designate.

  I have the sink running and this picks up the notification if you have
  the neutron_floatingip handler but this is for something else. I think
  this needs to be modified to also handle the reverse PTR records
  (managed_resource_type = ptr:floatingip)

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