lock wait timeout in create_dhcp_port
Bug #1313851 reported by
Salvatore Orlando
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Rossella Sblendido |
Bug Description
Apparent root cause: concurrent dhcp port operations with "offending" yield during create port.
Occurences: 8 in 7 days (failure rate: 50%)
Changed in neutron: | |
assignee: | nobody → Rossella Sblendido (rossella-o) |
Changed in neutron: | |
milestone: | juno-1 → juno-2 |
Changed in neutron: | |
status: | New → Confirmed |
Changed in neutron: | |
milestone: | juno-2 → juno-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
The lock scenario could go as follows: we see in the log that sync_routers() is called. It opens txn, then calls to _ensure_ host_set_ on_ports( ), which lower in the stack calls to plugin. update_ port(), which notifies and yields. Then we switch to a thread that updates port state, lock on that, and finally timeout.