Reservations code triggers deadlocks and lock wait timeouts
Bug #1486134 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
Switching the gate tests to multiple workers + pymysql is triggering a lot of errors like [1] in the reservation logic.
These errors are not hitting the gate at the moment (no instance of lock wait timeout or deadlock errors emerged from logstash).
Nevertheless Rally failure rate has now jumped to 100%. This means that the issue with the reservation logic will surely end up affecting production environments, and is a time bomb waiting to explode in the upstream gate.
The logic must be fixed, otherwise reverted.
Please also cut the fingers of the developer that wrote that code.
Changed in neutron: | |
milestone: | none → liberty-rc1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | liberty-rc1 → 7.0.0 |
To post a comment you must log in.
Related fix proposed to branch: master /review. openstack. org/214282
Review: https:/