Data Migration form FOG 0.32 to 1.2
-
Update on the issue. It seems to only happen from the basic tasks menu on hosts. If I go directly to active tasks menu and create a download there it will work. But on host basic task download menu its a no go. And it is not even thinking about it it just sends me the error in half a second.
-
i don’t understand what you mean. there is no method to create a task from the active tasks page.
-
Sorry I meant the task management. Let me put it clearer sorry
What’s not working:
When looking to a host configuration and clicking on basic tasks, you cannot perform a download from there. It pops up an error message saying there needs to be an image uploaded first (which there is already one). No scans no look nothing its instant as if no connection between this option and the database was made.
What is working:
When going to either Host management OR Task management under search host or list all hosts and clicking on the deploy arrow. This creates the download task and is ready to go.
In other words, it is not the whole download/deploy option that is broken, it is just that link under basic tasks in the host configuration page.
-
before a task gets generated the interface checks if an image has been assigned in the database, and it checks by ftp if the image exists on the storage node. this check is always pretty much “instant” in my experience.i believe it does the same checks no matter what button you use to create the task, but i could be wrong.
-
Which then makes it a weird bug… here’s some pictures, one of the error message when using the download option in the basic tasks, the other one after clicking on the download arrow from the hosts list.
[url=http://postimg.org/image/gjlko9f7p/][img]http://s10.postimg.org/gjlko9f7p/for_no_work.jpg[/img][/url]
[url=http://postimg.org/image/nwr32xsoj/][img]http://s21.postimg.org/nwr32xsoj/Fog_work.jpg[/img][/url]
-
ok, i’m told that the quick task button doesn’t perform this check. this points to a problem with the ftp running on your storage node
-
We do not use an FTP. This node is sitting in an NFS drive. Is the FTP check something new? it wasn’t giving me the error in version 0.32.
-
No, FTP is not new.
NFS is the “syncing” of the folders and FTP is the method to run commands to the node.
(This is in basic terms so that may not be the perfect way of saying this.) -
So do I need to create an FTP on my ftp server using Fog’s credential pointing to the node? how exactly is FTP connection will work on a machine or folder location that is not sitting in FTP?
-
WOW. Mass confusion…
What is the set up your are trying to accomplish?
-
haha sorry about that
FOG-server and DB are sitting on a Ubuntu 13.10 VM.
Image node is on an NFS share sitting on a Windows 2003 server (will be upgraded to 2008 R2 or 2012R2 soon enough)Basically I just want to get rid of that error message when doing the download from the basic tasks.
-
the storage location MUST have access to both NFS and FTP. without FTP you will get the error you just did, and after uploads the server will not be able to move the image from the /images/dev/<mac address> location to /images/<image name>
-
[url]http://www.fogproject.org/wiki/index.php/Windows_Storage_Node[/url]
If you notice in the tutorial there is an ftp program that is required it is called [B][SIZE=13px][FONT=sans-serif][COLOR=#000000]Filezilla[/COLOR][/FONT][/SIZE][/B]. You may want to look over the guide again and check your settings.
-
Ok I changed the node location to another server we have NFS and FTP setup already. Im uploading the image and will test the download after.
Stay tuned for the update!
ps: sorry for all those questions -_-
-
Nope! definitely we need to look at something else. Same error. Something changed though, no more errors after upload to change file name as I was getting before. Before after upload I would get those errors but image would still be moved from dev to /images after. Now it moves and no errors show up.
BUT the download error coming from the link in Host management still is a no go. FTP is enabled, user has full control and is even owner of the /images folder as well as its parent.
-
In the tutorial it is only used for a secondary storage node. I’m guessing you wish to have the windows node as the primary. You will need to make that change to the storage management section if not done so already.
-
Yes the node was set to master already. Also I changed the node from the windows 2003 server to a freenas server.
-
Alright
I’m getting lost in your setup Mathieu.
I’m all about customization, but you’re not sure where things are failing, and we haven’t a clue about your particular setup.
Why not restart and start simple first. Meaning, install fog and test it on a completely localized setup first. Ensure things work and work properly. Then start integrating the customizations.
One, you’ll learn a TON more about how fog works and what’s happening. Two you learn about many of the limitations.
I’ve never heard of people just adding and changing things in such a fashion before.
-
Tom, sorry if this confused you. The initial set up was already tested on local (Ubuntu 13.10 VM) and was working. nothing really has changed besides putting the master Node on a freenas (with FTP & NFS) and giving full control of the loaction to the fog user (which was put as the user to use in the node management on the GUI)
Since then, everything is still working fine, comunication between Fog and the node is fine, image uploads are going to the dev folder then after upload is finished it’s being transfered to the main /images folder. the ONLY issue is whenever we try to proceed a download from the host management page, it fails automatically giving out the error I posted above. BUT using the quick download from the host list in task management works.
Do you need more information?
