Hide Forgot
Description of problem: ================================== Running a imagefactory build image and the system ran out of file system space. Before the build process, image factory does a check for space but once the image is built, it copies the image into iwhd. It is on the copy operation where the system ran out of space. We should either check for double space initially before the build or add another space check before the copy operation. Version-Release number of selected component (if applicable): ====================================================================== imagefactory-0.7.0-1.el6.noarch imagefactory-jeosconf-ec2-fedora-0.1.0-1.el6.noarch imagefactory-jeosconf-ec2-rhel-0.1.0-1.el6.noarch iwhd-0.98.15.z3-2.el6.x86_64 oz-0.7.0-3.el6.noarch rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.el6.noarch
This check should be done by iwhd. imagefactory doesn't (and shouldn't) assume iwhd or any other component is on the same system or using the same storage. imagefactory can really only be responsible for itself.
Fair enough, re-opening against image warehouse. Basically a check is need in warehouse to ensure there is enough space on the filesystem before it accepts a image being copied into it otherwise we run the risk of filling up the file system and being left with a corrupted image.
adding to sprint tracker
k.. this is getting bumped to 1.1. I will be opening a bug for iwhd guys to clearly document disaster recovery steps. That will include recovery for out of space, corrupted images etc..
moving version to 1.0.0 . version = found in version