Transfer Images from 0.32 to fresh 1.2.0 - 1.2.0 can't see images
-
P.S. Just for FYI - the parameter we changed was for the image. The old Fog had it set to MPI - All Disks (Not resizable), and we had set it on the new Fog to MPI - Single Disk (NR), so now when it gets to ‘Checking Hard Disk’, we get ‘Done’ instead of that error
-
This post is deleted! -
Just a quick FYI update - we set the VM to PXE boot, create the task in Fog to deploy to the ‘seen’ VM, it boots up, goes through the initial Fog cmd screen, then at the end - reboots - and it’s at THIS point it reboots into the Fog GUI with the ‘Quick Image’ listed as a choice, so from what we know, the imaging should have happened during the initial boot and NOT reboot (if we have this right), so that kind of suggests that it’s not seeing the image on the initial boot up.
BTW - we made the drive 5GB’s bigger than the actual system (a laptop) that this ‘test’ image was created for, and we set it as IDE, so don’t know if any of that info matters
-
This post is deleted! -
Still trying to see if we’ve missed something, so going through the settings - again
-
Haven’t updated in a while, but after digging on the web a bit more these past few weeks, found a note that it may be due to the old image ID’s still being in play somewhere, so you need to reset them. We’re rebuilding the current server from scratch and going to see what the DB shows when we transfer the ‘Test’ image across. Will update again.
-
I’m having issues using images that I transferred from my previous 0.32 server, to my 1.2 server. So far I have copied the image to the /images folder, and created the"image profile" in the FOG GUI and named it exactly like the file I transferred. I went into the settings and turned on the FLAG_IN_GUI option and set that image to partimage. I’m still receiving this error when I try to deploy this image to a host.
I also created a new image directly from the server and uploaded an image to it, and strangely i’m not seeing the file that should have been added to the /images folder with that images name.
I’m running FOG on Ubuntu 14. I’m not sure if this is a permissions error for the /images folder?
-
@cassie_280 FOG 1.2.0 is notorious for FTP Credentials issues… I’d suspect that it’s either a credentials problem, or the path is not exactly how it should be. the pathnames are case sensitive. Also you need to ensure the right permissions exist on time image you moved in. Look at this:
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
and make sure the image you moved has 777 permissions recursively like this:
chmod -R 777 /images -
FWIW: On my centos system the permissions are 755 and owned by fog.fog for all files and folders in /images
-
@Wayne-Workman It’s weird. I realized that I can do a full host registration and image from the machines and it works fine. It only fails when I try to deploy the image from the server.
-
@cassie_280 What version of FOG are you using? What is the number in the cloud, top left?
Is it possible that there are two fog servers in your environment, and you’re just using the wrong/old one?
-
@Wayne-Workman I do have two FOG servers, but the old one is shut down, so I’m positive that’s not the one I’m using. I’m using FOG version 1.2.0
-
@cassie_280 have you gone through the credentials section of the below article, “Troubleshoot FTP” ?
-
@Wayne-Workman That’s what my problem was. I changed my su password. I didn’t realize that affected the FTP credentials. Once I changed the other locations to match, everything worked perfectly. Thank You!