need_longer_timeout_setting_for_solidfire_clone
Bug #1202007 reported by
John Griffith
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
John Griffith | ||
Grizzly |
Fix Released
|
High
|
John Griffith |
Bug Description
Current timeout value for clone volume in the SolidFire driver is 20 seconds, this is fine in many cases however there seems to be a number of customers doing clones of volumes >= 400G. A populated 400G volume is taking upwards of 35 seconds in some cases resulting in failure.
There's no reason not to bump this timeout value up significantly to a worst case scenario (ie multi-terrabyte volume).
Changed in cinder: | |
importance: | Undecided → High |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
tags: | removed: grizzly-backport-potential |
Changed in cinder: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/37358
Review: https:/