xenapi: Detecting bad-volumes relies on 120 sec timeout

Bug #1152401 reported by Rick Harris
8
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.

Tags: xenserver
Changed in nova:
importance: Undecided → Critical
status: New → Confirmed
Mate Lakat (mate-lakat)
tags: added: xenserver
Revision history for this message
Bob Ball (bob-ball) wrote :

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.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :
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 :
Changed in nova:
status: Triaged → In Progress
Revision history for this message
John Garbutt (johngarbutt) wrote :

There is a fix for the big issue here, but it would be good to do better, so moving this to low

Changed in nova:
assignee: Bob Ball (bob-ball) → nobody
importance: High → Low
status: In Progress → Confirmed
Changed in nova:
importance: Low → Wishlist
Sean Dague (sdague)
Changed in nova:
status: Confirmed → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.