/tmp space near full causes failure of create from image
Bug #1217552 reported by
Jeff Applewhite
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Eric Harney |
Bug Description
when a cinder create using an --image-id as source for the volume happens in conjunction with inadequate space free on /tmp the create fails due to the conversion to bare format running out of disk space.
converting in /tmp seems to me to be a reasonable choice at first but not when you consider that image files in glance can be quite large. Doesn't cinder need some way to allow defining the conversion space to be somewhere other than /tmp. Many conversions will happen on VM's with small memory and disk footprints. Perhaps the conversion would better take place somewhere defined by the admin?
Changed in cinder: | |
importance: | Medium → High |
importance: | High → Undecided |
Changed in cinder: | |
importance: | Undecided → Medium |
Changed in cinder: | |
milestone: | none → havana-rc1 |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
You can redefine this dir with the setting: conversion_ dir=/tmp
# parent dir for tempdir used for image conversion (string
# value)
#image_
But, I am not particularly convinced that /tmp is the best default for this as opposed to something like $state_ path/conversion . Needs some thought here IMO.