Unable to deploy images on 1.5.7



  • I have just upgraded from 1.5.6 to 1.5.7 and I am getting the following error message when trying to deploy any images.

    Init Version: 20190714
    No file to receive from passed (restoreEBR)
    	Args Passed: /dev/sda1 /tmp/d1p1.ebr
    
    Kernel variables and settings:
    loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.10.10.1/fog/ consoleblank=0 rootfstype=ext4 mac= ftp=10.10.10.1 storage=10.10.10.1:/images/ storageip=10.10.10.1 osid=5 irqpoll chkdsk=0 img=Win7Prox6420-05-19 imgType=n imgPartitionType=all imgid=2 imgformat=0 capone=1 type=down
    

    The images were created using the default settings in either v1.5.5 or 1.5.6

    The upgrade was done using the download from https://fogproject.org/download rather than using git.
    Does anyone have any idea what would cause this or how to fix it?

    I have rolled back to 1.5.6 for now but can re-apply the upgrade if any more info is required.

    Thanks in advance.


  • Senior Developer

    @kafluke Arrrrgh, just found out that the installer does not re-download the hash file to see if the binaries (kernels and inits) package changed on the webserver. Should change that!

    So to fix the issue, run rm fogproject/tmp/binaries1.5.7.* and then re-run the installer.



  • Just got round to reapplying the upgrade and testing. Everything seems to working perfectly now.

    Thanks for the quick response and fix.


  • Senior Developer

    @kafluke Arrrrgh, just found out that the installer does not re-download the hash file to see if the binaries (kernels and inits) package changed on the webserver. Should change that!

    So to fix the issue, run rm fogproject/tmp/binaries1.5.7.* and then re-run the installer.



  • @Sebastian-Roth I just updated to 1.5.7 and I’m still getting the same error.



  • @Sebastian-Roth Working like a champ on mine:) As always I appreciate the speedy support:)


  • Senior Developer

    @Jethrov @kafluke @Mx7Nine I just updated the inits. So updating to 1.5.7 should be save now. Sorry again for the hickup! Please test and let us know.

    About rolling back: It’s not officially supported to roll back to an earlier version because taking back some of the database changes we do from one version to the other can’t be reverted easily if entries were added based on the new table structure. Most often you can still just get the earlier installer and install that over the newer to get the earlier version. But as I said, it can cause real bad trouble and we don’t support rolling back.

    Best what you can do is take a snapshot/backup of the VM/server before upgrading and stepping back will be easy then because it also rolls back the database (entries and structure).



  • I am having the same exact issue. I will wait on the fix if it’s going to only be a couple of hours though. But just because I am curious, I would also be interested in the instructions on how to roll the updates back as well.


  • Senior Developer

    @Mx7Nine @kafluke Thanks for reporting and sorry for that. Something I messed up obviously. Will be fixed within the next two hours!



  • never mind I figured out how to roll back.



  • Can you tell me how you rolled back to 1.5.6? I need to do the same asap!



  • I’m having this exact same issue after upgrading this morning


Log in to reply
 

316
Online

7.5k
Users

14.6k
Topics

137.8k
Posts