This looks like a different issue. The problem you have identified is specific to a DHCP agent port being deleted.
Shraddha's question seems to be about all ports. All of the port information is synced on startup via sync_state here: https://github.com/openstack/neutron/blob/master/neutron/agent/dhcp/agent.py#L147 so there shouldn't be any issues there. On Tue, Jun 30, 2015 at 7:09 PM, shihanzhang <[email protected]> wrote: > hi Shraddha Pandhe, > I think your analysis is right, I also encountered the same problem， I > have filed a bug[1] and commit a patch [2] for this bug. > > thanks, > hanzhang shi > > [1] https://launchpad.net/bugs/1469615 > [2] https://review.openstack.org/#/c/196927/ > > > 在 2015-07-01 08:25:48，"Shraddha Pandhe" <[email protected]> 写道： > > Hi folks.. > > I have a question about neutron dhcp agent restart scenario. It seems > like, when the agent restarts, it recovers the known network IDs in cache, > but we don't recover the known ports [1]. > > So if a port that was present before agent restarted, is deleted after > agent restart, the agent wont have it in its cache. So port here [2] will > be None. So the port will actually never get deleted. > > Same problem will happen if a port is updated. Has anyone seen these > issues? Am I missing something? > > [1] > https://github.com/openstack/neutron/blob/master/neutron/agent/dhcp/agent.py#L82-L87 > [2] > https://github.com/openstack/neutron/blob/master/neutron/agent/dhcp/agent.py#L349 > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kevin Benton
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
