Images missing from OnD after update. Workaround included.

  1. last year
    Edited last year by jmn

    I believe that I have found a bug and a possible workaround for others in the same situation. I has happened on 2 different servers.


    I had a version 1.0.1p3 before the update.
    My image storage was moved to D:\clonedeploy\ and worked fine.
    Edit: Running on Windows Server 2012R2.

    What happened:

    Followed instructions to the letter and update to 1.1 was successful.
    When I tried to pxeboot to On Demand deployment, all of my images were gone.
    However, in the web interface they were all still there and seemingly nothing had changed. I tried creating a new image in the web interface and found out that on the image search overview, the old images had nothing below Imaging Environment while the newly created one said linux.
    I tried to update the images with new names, but it didn't help. The drop-down menu for Client Imaging Environment was not responsive.


    The workaround for this is to create new images and then copy the files and folders from the old images into the folders of the new ones. It will then work and you can boot from them again.

  2. clonedeploy

    27 Jun 2016 Administrator

    Thanks for reporting this. I'll release a fix soon.

  3. Thank you for a great program and the service you provide.

  4. Edited last year by Spiker985

    Can confirm, happened to me after upgrade. Didn't make any changes to my setup. The included work around appears to have worked.

  5. clonedeploy

    5 Jul 2016 Administrator

    Was fixed in 1.1.1

  6. I'm on 1.1.1. Unless I did something wrong, which it doesn't seem like I did.

  7. clonedeploy

    5 Jul 2016 Administrator

    Will need to wait for feedback from others. Working for me

  8. Maybe my issue was entirely different, but looked the same. I wasn't able to use my images after the upgrade because they didn't have the "Linux" tag for the Imaging Environment.

    1. I made a new image with all the settings I needed.
    2. Renamed the appropriate folder in cd_dp for the previous image (pre 1.1.1) to name.bak.
    3. Deleted the listed image in CD.
    4. Renamed the newly created 1.1.1 image, to the previous name
    5. Deleted the empty folder and renamed the name.bak back to name.

    I don't know if that made sense, but that's all I had to do to fix it.

  9. clonedeploy

    6 Jul 2016 Administrator

    Yes that makes sense, but I just tested this entire process and seems to be working.
    Installed 1.0.1
    Captured an image
    Updated to 1.1.0
    Updated to 1.1.1
    Deployed the image from both web and on demand and both worked


or Sign Up to reply!