DVR scheduling checks wrong port binding profile for host in live-migration
Bug #1776255 reported by
Kailun Qin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Kailun Qin |
Bug Description
When live-migrating, active l3 agents on compute nodes will request a router sync against DVR routers impacted by the migration. This will check for existence of dvr serviceable ports on host to further filter the router applicable to it. However, the current implementation performs a "contains" operation on the port binding profile for host which will produce a LIKE expression that tests against a match for the middle of a string value: column LIKE '%' || <host> || '%' [1]. This leads to a wrong filtering due to the sub-string match (i.e. compute-1 will match compute-10).
Example binding profile (dict) for host:
{
"binding:
}
Changed in neutron: | |
assignee: | nobody → Kailun Qin (kailun.qin) |
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: l3-dvr-backlog pike-backport-potential queens-backport-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | added: neutron-easy-proactive-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/574370
Review: https:/