I’m not sure what’s going on behind the scenes so take this with a grain of salt. What do you expect to see after the HD has been formatted? (I don’t think you’re formatting but whatever it is that nukes the OS). The script try’s to copy “something” and ultimately can’t find it. A check could be done prior to the formatting stage to make sure that something exists.

You’re both correct. Fog isn’t creating empty directories. I created the empty directory by hand while I was troubleshooting an issue. This was an error on my part plain and simple. However, it’s not uncommon for admins to move things around outside of the Fog admin interface.

I suggest adding a feature to check for the existence of the image prior to imaging.

[B]Fog doesn’t check to ensure an image exists in source directory before wiping target computer.[/B] So long as the directory for the image is present, Fog assumes an image is present and proceeds to wipe any computers tasked to install said image before finally failing because it can’t find the image.

A check needs to be done to ensure an image exists in said directory prior to starting the imaging process. The mere presence of a directory isn’t enough.

Fortunately, I found this out while testing so it didn’t cause any damage.

PS: Is this the correct place to submit bug reports or is there a bug tracker somewhere?

Thanks

I’ve run into the same issue and believe I can reproduce the error. In order to test my theory I’ll first need to know how to delete the FOG db and re-run setup. How did you delete the DB so I can re-run setup?

After I’ve fixed my install I’ll see if I can break it again and report back on how I did it.