• VM template stuck at updating due to wrong vdisk path

    Ver7o

    By Ver7o

      • Minor

    This is an issue described here in this topic. I decided to post it under here becase @jonp showed interest in debugging it. 

     

    Quote

     

    I have a VM named Spynet, which has a correct vdisk path by /mnt/user/domains/Skynet/vdisk1.iso

     

    Whenever I edit the template, the template thinks the vdisk location is /mnt/user/domains/Spynet/vdisk1.iso which doesnt actually exist and results in the that dreaded Updating...

     

    The bug here would be, that the template does not remember the manual location and always reverts to auto which always looks for the vdisk inside the VMs namesake folder.

     

     

    Basically, the reason the VM template hangs at updating is because, the template itself has a wrong path to the vdisk (always uses its VM namesake folder), and no matter how many times you correct it manually, upon next edit it will not remember the correct location.

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    -Daedalus

    Yeah, I remember bonienl saying this was fixed in the next 6.9 beta. 

    (I remember because this one bugs the hell out of me on 6.8.3. 😋)

    Edited by -Daedalus
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.