yahoo-eng-team team mailing list archive

[OpenStack Infra <1696010@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/471154
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=781b8f41498521041f7c9d4b4e0c0fa438736fc4
Submitter: Jenkins
Branch:    master

commit 781b8f41498521041f7c9d4b4e0c0fa438736fc4
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Mon Jun 5 15:50:34 2017 -0700

    Stop binding attempts when network has no segments
    
    There is no point in retrying binding if the network has no
    segments to bind to. This occurs during normal operations when
    a network is being quickly created/deleted and the DHCP port
    gets created during the network deletion.
    
    By skipping binding we avoid misleading error messages and
    wasted CPU cycles.
    
    Closes-Bug: #1696010
    Change-Id: I0b987ab7c3f65c1d860064a1b437b92a1dc1cb81


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  binding errors during network deletion

Status in neutron:
  Fix Released

Bug description:
  The server logs have several errors like the following:

  Jun 02 21:08:04.559663 ubuntu-xenial-citycloud-lon1-9112444 neutron-
  server[18208]: ERROR neutron.plugins.ml2.managers [None req-
  9d2a2fbc-f777-4b55-8390-bfafc514668f None None] Failed to bind port
  03819448-f86f-4d2b-810b-a456366c3afb on host ubuntu-xenial-citycloud-
  lon1-9112444 for vnic_type normal using segments []

  
  These occur while a port is trying to bind while the network is being deleted. We should just stop binding attempts if there are no segments.

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