yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #48491
[Bug 1560221] Re: No port create notifications received for DHCP subnet creation nor router interface attach
** Also affects: searchlight
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1560221
Title:
No port create notifications received for DHCP subnet creation nor
router interface attach
Status in neutron:
New
Status in OpenStack Search (Searchlight):
New
Bug description:
Creating a subnet with DHCP enabled either creates or updates a port
with device_owner network:dhcp matching the network id to which the
subnet belongs. While there is a notification received for the subnet
creation, the port creation or update is implicit and has not
necessarily taken place when the subnet creation event is received
(and similarly we don't get a notification that the port has changed
or been deleted when the subnet has DHCP disabled).
My specific use case is that we're trying to index resource
create/update/delete events for searchlight and we cannot track the
network DHCP ports in the same way as we can ports created explicitly
or as part of nova instance boots.
The same problem exists for router interface:attach events, though
with a difference that we do at least get a notification indicating
the port id created. It would be nice if the ports created when
attaching a router to a network also sent port.create notifications.
Tested under mitaka RC-1 (or very close to) with 'messaging' as the
notification driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1560221/+subscriptions
References