• [6.8.3] VMs marked as autostart do not start after stopping and restarting array


    ElectricBadger
    • Minor

    After stopping and starting the array, VMs set to autostart are not started, while Docker containers marked as autostart are.

     

    Reproduction steps:

     

    1. Install two Docker containers: letsencrypt and emby. Set the letsencrypt container to autostart, but leave autostart disabled on the emby container.
    2. Start both containers manually if they are not already started.
    3. Create two VMs called a and b. Set a to autostart, but leave autostart disabled on b.
    4. Start both VMs manually if they are not already started.
    5. Go to Main and stop the array.
    6. Start the array.
    7. Go to Docker and verify the state of the containers.
    8. Go to VMs and verify the state of the VMs.

     

    Expected behaviour:

     

    The letsencrypt container and the a VM are started. The emby container and the b VM are stopped.

     

    Actual behaviour:

     

    The letsencrypt container is started. The emby container is stopped, as are both VMs — the autostart setting has been ignored for VMs.

     

    (In case it shows in the diagnostics: I had already restarted one VM manually when I remembered I needed to grab diagnostics :)

    celestia-diagnostics-20200625-0918.zip




    User Feedback

    Recommended Comments

    I'm seeing the same behavior on 6.9.0-b25.  If I stop the array make a change and re-start all dockers that are supposed to autostart are starting.  I've got 2 VMs (one set to autostart) and it doesn't start when I start the array.

    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.