Public bug reported: 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 ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- 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: New 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
