HOW to upgrade from trunk SVN 5850 to 1.4.0 stable?



  • Server
    • FOG Version: trunk
    • OS: Fedora 23 server
    Client
    • Service Version:
    • OS:
    Description

    Hello !
    I’m a network administrator for a french High-School (so sorry if my english is bad).

    Last year I have installed fog trunk on Fedora 23 Server, now we work with the 5850 SVN revision.

    Recently I have saw the new stable version available (1.4.0) and trying to upgrade my FOG to this version.

    In first i have install fedora 23 server in virtual machine (to safe my clean server :-D ) and install fog 1.4.0.

    next i have import my old database to the new fog with this process : https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG. And I have transfered 1 image + the “dev” and “postscriptdownloads” directorys in the “images” directory of my new server.

    Now there are 2 problems.
    The first is the database transfert, when i import the old database and go back to the web interface of fog, I have the database install page. Because I can directly see when I navigate in the interface, the trunk database and the 1.4.0 database are very different.

    The second is about image deployement. I have try to deploy the image on computer but after transfert an error occured and the computer don’t boot.

    So please can you help me to upgrade my FOG server to stable version whithout recreat all images I have in my fog trunk?

    Cordially



  • @Junkhacker pigz !! this the error I had when I’m trying to deploy with Gzip otpion on the 1.4.0.

    Thanks for this precision

    @Wayne Workman

    I have tried many solution to import my images from the old server to a new in 1.4.0 but nothing working.

    I think the one solution is two deploy each image from the old server to a master and capture this image with the new serveur.

    So I have testing this way it’s working.

    Next just in case off I have created an other 1.4.0 server (yes 3 servers in the story) to test a migration between the two 1.4.0 servers with this process : https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG. All work fine.

    Even if this was not the aim methode I serched to migrate my old images to the new, I think we can close this topic ?

    Thanks all for help it’s very nice.


  • Developer

    @Wayne-Workman a couple minor corrections. the last official release to capture using partimage was 0.32, i think. images have always been gzip compressed. between 1.2 and 1.3 the program for decompressing was switched to pigz. pigz is a parallel (multi-threading) implementation of gzip compression, which sped it up a bit.


  • Moderator

    @EagleEnergy We need you to move to the latest stable fog release 1.4. I’m fairly certain the issue you have with zstd is already fixed in 1.4.

    sudo -i
    dnf -y update
    dnf -y install git
    git clone https://github.com/FOGProject/fogproject.git
    cd fogproject/bin
    ./installfog.sh -y
    


  • @Wayne-Workman Thanks you for the clarifycation, I think I’m between 1.2 and 1.3 so the good option is partclone Gzip.

    Here I redeploy an image with this option but an error appears again at the end of deployement (I expected that).

    So now i’m trying to use you’r postinit.sh scripts to analyse the problem, but the scripts can’t work because he doesn’t found the funcs.sh file in /usr/share/fog/lib directory.

    I don’t know if it’s because I use fedora but I don’t have /usr/share/fog directory in my server.


  • Moderator

    @EagleEnergy I don’t know when FOG started using partclone, but somewhere around 1.0 and lower used partimage with pigz compression. between 1.2 and 1.3 gzip was adopted. Somewhere between 1.3 and 1.4 zstd was adopted. When importing those old images, you’d just have to choose those settings.



  • @Wayne-Workman This is the problem I don’t found the same settings of the old server.

    On the version of my old server I don’t have the choice between differents type of partclone or partimage. It’s just said the image was created with partclone but I don’t know what is the same option in 1.4.0 version :confused:

    This is the capture from the old server
    0_1496130355071_Sans titre.jpg


  • Moderator

    @EagleEnergy The process is the same, but we do have a guide here: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

    The image only needs recaptured if the settings change. If you keep the same settings the old server had, you don’t need to re-capture.



  • @Wayne-Workman Ho OK. The once solution is to deploy an image with old server And recapture him with the New ?

    And just in case off, in the future if I want to migrate images from a 1.4.0 server to an other 1.4.0, the process is the same or just moving images with ftp for exemple ?


  • Moderator

    @EagleEnergy said in HOW to upgrade from trunk SVN 5850 to 1.4.0 stable?:

    So no I don’t recapture the image after changing settings

    If you change the image’s settings, you must re-capture that image.



  • @Quazz “4th: I have recreated the 3 images in the new server (3 windows 7 with multipartions single disk option).”

    I have use the Single Disk Multiple Partition for the 3 images because there are W7

    So no I don’t recapture the image after changing settings because the idea is the backup the images from the old server to the newest. (The images work perfectly with the old server)

    Tomorrow I upload the partclone log ;)

    Thanks again for help


  • Moderator

    Can you try again with image type of Single Disk Multiple Partition ?

    And just to verify, you do recapture the image after changing the image settings, correct?

    The partclone log would be very useful though, so hopefully you can provide this tomorrow.



  • Hello guys !

    So this what I had do today:

    1st: I have reinstall a new clean 1.4.0 FOG server

    2nd: I have upload 3 images directory, “dev” directory and the “postdownloadscripts” directory from the old server to the new in /images where I have replaced de two “dev” and “postdownloadscripts” directorys.

    3dr: I have import the host_export.csv from the old server to the newest.

    4th: I have recreated the 3 images in the new server (3 windows 7 with multipartions single disk option).

    5th: I have test to deploy the 3 images with 3 différente way off partclone.
    the first image was deployed with partclone gzip option.
    the second image was deployed with partclone zstd option
    and the third image was deployed with partclone uncompressed option.

    6th: For the partclone gzip and zstd I had an error at the end of deployement.
    For the partclone uncompressed, the deployement doesn’t start.

    @Wayne-Workman I doesn’t had the time to test your script, maybe tomorrow.

    This the exemple of error for partclone gzip and zstd:
    ![alt text](0_1496070267914_IMG_20170529_154212.jpg image url)
    0_1496070280176_IMG_20170529_154217.jpg
    0_1496070292367_IMG_20170529_164216.jpg

    On the old server I just know image are created with partclone but there are no options In this version of FOG.



  • Thanks you guys. I will trying yours solutions at Monday.

    I have tried before to recreate one image but not the time to test to deploy it.

    @Wayne-Workman : Think you for the script.

    @Quazz: I will finish the test of your solution.

    I will reporting to you guys news about yours propositions.

    Thanks you


  • Moderator

    @Quazz said in HOW to upgrade from trunk SVN 5850 to 1.4.0 stable?:

    At any rate, since the error is partclone related, can we get the specific error? The answer will vary depending on it.

    This postinitscript packages everything in /var/log of FOS and sends it to a windows share (and other cool stuff): https://github.com/FOGProject/fog-community-scripts/blob/master/fogAutomatedTesting/postinit.sh

    Works whether image deployment pukes on itself or not. This would include the full partclone log and /var/log/messages and other things.


  • Moderator

    @EagleEnergy said in HOW to upgrade from trunk SVN 5850 to 1.4.0 stable?:

    The first is the database transfert, when i import the old database and go back to the web interface of fog, I have the database install page. Because I can directly see when I navigate in the interface, the trunk database and the 1.4.0 database are very different.

    That’s intended. When we import an older database, FOG can upgrade it to the current schema version. There should be a big fat button center-screen that says update database or something similar.



  • @Quazz said in HOW to upgrade from trunk SVN 5850 to 1.4.0 stable?:

    FOG has added new options for the image manager, it’s possible that this is causing issues for you (I seem to recall someone else having issues having with it, too).

    This is what I think also because fields of settings between my version (8450) and the 1.4.0


  • Moderator

    @EagleEnergy Yes, but at the end of deployment FOG contacts the database, when this fails it will mention such.

    At any rate, since the error is partclone related, can we get the specific error? The answer will vary depending on it.

    Additionally, if you could share the settings for the image you’re trying to deploy (the image definition settings)

    FOG has added new options for the image manager, it’s possible that this is causing issues for you (I seem to recall someone else having issues having with it, too).



  • @Quazz
    Hmmm nice idea I don’t have try to recreate the definitions of imported images.
    I will testing it.

    For the error I had no time to read it sorry if I have time, I’m going to recreate the same process and capture the moment with my phone.

    Thinks you for help me

    [EDIT]:
    Sorry I just have understand your question about the error.

    the error is not about the database, is about image deployement.
    I can start deployement to client computer but at the end of the process I have an partclone error and the computer reboot corrupted


  • Moderator

    There should be a button to update the database on the web interface, this should update the relevant tables and it should work fine.

    If worst comes to worst and the database is unusable (unlikely), then it’s no problem because you can copy the image folders over and recreate the definitions for them and it will work.

    Can you tell us more about the error you got? I’m guessing it’s going to be the Unable to update database one.


Log in to reply
 

917
Online

39.4k
Users

11.1k
Topics

105.5k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.