yahoo-eng-team team mailing list archive

[OpenStack Infra <1648879@xxxxxxxxxxxxxxxxxx>]

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

commit a5a8a37344f6d193886ae8d047664aef76920ed8
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Fri Dec 9 11:49:09 2016 -0800

    Check for unbound ports in L3 RPC handler
    
    The handler was making the incorrect assumption that once a
    host_id was set, a port which failed to bind could only be in
    the 'binding_failed' state. So it would not try to rebind ports
    that encountered an exeption during port binding commit that left
    them in the unbound state.
    
    Change-Id: I28bbeda5fed4275ea38e27308518f89df9ab4eff
    Closes-Bug: #1648879


** 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/1648879

Title:
  l3 rpc handler not checking for UNBOUND with host_id

Status in neutron:
  Fix Released

Bug description:
  If a binding fails to commit after a host_id is set on a port, the
  port will have a host_id with a vif type of 'unbound'. In this case
  the L3 RPC handler should be trying to update the port again as it
  would when the binding had changed the vif type to binding_failed.
  However, it currently doesn't due to a bad conditional[1].

  
  1. https://github.com/openstack/neutron/blob/5254f0ab60d46cabdace6d59ce50ca05568a87d5/neutron/api/rpc/handlers/l3_rpc.py#L141-L142

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