'binding:host_id' is set None when port update without portbinding changes
Bug #1245310 reported by
Hyunsun Moon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Hyunsun Moon |
Bug Description
When I try to update port for additional fixed IP or any other attributes other than portbinding, _process_
It may not be a problem if the agents do not use portbinding information but if the agent uses 'binding:host_id' information for port update it will cause a problem, which is in my case.
When look at the codes, Neutron server sets 'binding:host_id' to 'None' as long as 'binding:host_id' is not in the requested update items. It should query DB to set correct port binding instead of 'None' in that case.
description: | updated |
Changed in neutron: | |
assignee: | nobody → Hyunsun Moon (hyunsun-moon) |
status: | New → In Progress |
Changed in neutron: | |
status: | Incomplete → In Progress |
Changed in neutron: | |
milestone: | none → icehouse-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
I could not reproduce this issue with port update.
Can you specify the list of commands I need to run to reproduce?
What plugin do you use?