xenapi: Detecting bad-volumes relies on 120 sec timeout
Bug #1152401 reported by
Rick Harris
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Opinion
|
Wishlist
|
Unassigned | ||
Bug Description
Currently the only known way to detect bad-volumes in XenServer is to perform a SR.scan which will hang for 120 seconds and then return an error.
This bug is to remind us to fix this in Nova when/if a patch from Citrix becomes available to allow us to 'fail-fast' here.
| Changed in nova: | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
| tags: | added: xenserver |
Revision history for this message
| Bob Ball (bob-ball) wrote | #1 |
Revision history for this message
| Davanum Srinivas (DIMS) (dims-v) wrote | #2 |
| Changed in nova: | |
| importance: | Critical → High |
| Changed in nova: | |
| status: | Confirmed → Triaged |
| Changed in nova: | |
| assignee: | nobody → Bob Ball (bob-ball) |
Revision history for this message
| John Garbutt (johngarbutt) wrote | #3 |
| Changed in nova: | |
| status: | Triaged → In Progress |
Revision history for this message
| John Garbutt (johngarbutt) wrote | #4 |
| Changed in nova: | |
| assignee: | Bob Ball (bob-ball) → nobody |
| importance: | High → Low |
| status: | In Progress → Confirmed |
| Changed in nova: | |
| importance: | Low → Wishlist |
| Changed in nova: | |
| status: | Confirmed → Opinion |
To post a comment you must log in.
Could you post the error message received when the eventual timeout occurs? I can then look at which piece is causing the timeout and hopefully find a quicker way to return.