l3 rpc handler not checking for UNBOUND with host_id
Bug #1648879 reported by
Kevin Benton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Kevin Benton |
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].
Changed in neutron: | |
assignee: | nobody → Kevin Benton (kevinbenton) |
tags: | added: neutron-proactive-backport-potential |
Changed in neutron: | |
importance: | Undecided → High |
tags: | removed: neutron-proactive-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/409314
Review: https:/