Hi Dan Thanks for the response. This is with one of our custom neutron ML2 mechanism drivers and that code is not yet upstream Nothing has changed in nova code though. We just use the Liberty version If I provide the nova and neutron logs would it be possible to provide some insights. I can log a bug for this Ajay
On 10/8/16, 5:41 PM, "Dan Smith" <d...@danplanet.com> wrote: >> Basically the issue is seen in the following three lines of nova compute >> log. For that port even though it received the vif plugging event 2 mins >> before it waits for it and blocks and times out >> Is there a race condition in the code that basically gets the events to >> wait for and the one where it registers for this callback >> Any comments? > >This shouldn't be possible because the point at which we call >plug_vifs() is when we should trigger neutron to fire the vif-plugged >event, and that is after where we have already setup to receive those >events. In other words, your log lines should never be able to be in the >order you showed. If it's happening in that order (especially two >minutes early) I would be highly suspect of some modifications or >something else weird going on. > >It'd be much better to handle this in the context of a bug, especially >providing the versions and components (i.e. neutron driver), etc. Can >you open one and provide all the usual details? I'll be happy to look. > >--Dan > >__________________________________________________________________________ >OpenStack Development Mailing List (not for usage questions) >Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
