• [6.10.0-rc5] - VM Manager service silently fails to stop


    tjb_altf4
    • Solved Minor

    I noticed this with rc4 (just before upgrading to rc5), but I had other one off issues so wanted to test after a few reboots/reinstalls...


    Now on RC5, if I try and stop the VM Manager like in the screenshot below, it fails to shutdown, as seen by the status.

    This also stops me from making network config changes, as expected when VM Manager is still running

    image.thumb.png.1d385794ba0da486ed61c2d8f54f3654.png

     

    Logs indicate the shutdown script has failed, note that I don't have any VMs defined yet (which may be the cause of the array error?)

    Apr 28 11:56:16 jaskier emhttpd: shcmd (395): /etc/rc.d/rc.libvirt stop
    Apr 28 11:56:16 jaskier root: /etc/rc.d/rc.libvirt: line 57: NAMES[${id:0:36}]: bad array subscript
    Apr 28 11:56:16 jaskier emhttpd: shcmd (395): exit status: 1
    Apr 28 11:56:16 jaskier emhttpd: shcmd (396): umount /etc/libvirt

     

    Further troubleshooting shows it definitely isn't stopped
    image.png.5fe27b2cc10d1bdd648a72463ece8b31.png




    User Feedback

    Recommended Comments

    Tested both with no VMs defined, and with 1 VM defined.

    In both cases the issue is resolved in 6.10.0-rc6, thanks!

    Edited by tjb_altf4
    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.