Potential race condition in l3-ha handling of l2pop initial master selection
Bug #1488015 reported by
Ihar Hrachyshka
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Low
|
venkata anil |
Bug Description
In _ensure_
The race could occur when we first fetch the active host for the port, it's returned as None because it's not yet elected, then it's elected, and only then we hit the database with our random host, so in the end the port binding contains the host that does not potentially reflect the master (assuming the agent that sent sync_routers() is not the one that became the master).
Changed in neutron: | |
status: | New → Confirmed |
tags: | added: l2-pop l3-ha |
Changed in neutron: | |
assignee: | nobody → Ann Kamyshnikova (akamyshnikova) |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | Ann Taraday (akamyshnikova) → venkata anil (anil-venkata) |
status: | Confirmed → In Progress |
Changed in neutron: | |
status: | In Progress → Won't Fix |
To post a comment you must log in.
As far this issues was not detected on real deployments mark down its importance.