No retries in 'network_set_host' function
Bug #1422610 reported by
Pavel Kholkin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Low
|
Pavel Kholkin | ||
Bug Description
In nova 'network_set_host' function could happen db_exc.DBDeadlock or the function could return 0 rows updated. These cases mean that concurrent transactions try to update the same row. In these cases we should retry the transactions and try to fetch another row to update.
| Changed in nova: | |
| assignee: | nobody → Pavel Kholkin (pkholkin) |
| Changed in nova: | |
| status: | New → In Progress |
| Changed in nova: | |
| importance: | Undecided → Low |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → kilo-3 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit f1935a55bc4e618
Author: pkholkin <email address hidden>
Date: Mon Feb 16 21:44:05 2015 +0400
Added retries in 'network_set_host' function
In concurrent transactions in 'network_set_host' function
could happen a deadlock or returned rows_updated value
could be equal to 0.
In these cases we should retry the transaction to get
another row and try to set the host again.
Closes-Bug: #1422610
Change-Id: I374b12e62f7681