-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multipass can't delete LXD instances that go into Error state #2492
Comments
I had the same issue and restarting lxd via snap fixed the issue. |
the same problem happened to me today. And now, How can I remove the VM? |
Hi @aatrcoutinho, until we get this fixed, you can delete instances in LXD directly: |
Lifesaver !! This worked for me too:
Huge Thanks @ricab as Multipass accidentally does serious damage (blocking deletion of the VM, and even blocking the host machine from rebooting) when Multipass effectively loses control of VM's like this one:
CLARIF: The above worked in recent weeks, but no longer works today, painfully freezing out many/most all Multipass actions. Even Hence the need to force the deletion of a Multipass VM using LXD. As Multipass itself is unfortunately not capable of reliably deleting its own VM's:
This lifesaving trick should be better documented within https://multipass.run/docs e.g. at remove-an-instance or some similar space, Thanks All! Background: |
To CLARIFY the above, even this very latest Edge Channel version of Multipass cannot reliably delete its own VM's / instances:
|
@holta, Multipass is designed to launch Ubuntu VMs, not Debian. You can try, of course, but you're on your own then. It might work, but it is no surprise that it doesn't. |
Just FYI Debian 12 instances worked fine with Multipass in the past. The Much Larger Point (this ticket!) is that Multipass accidentally sabotages the host PC (preventing the "reboot" command from working, etc) when any instance (Debian or Ubuntu or whatever, that's not the point) encounters everyday such testing errors. So your original request (thank you to @ricab) is quite important: Multipass indeed needs to evolve to be able to delete dysfunctional instances -- according to the instructions it provides, which for the moment is: https://multipass.run/docs/remove-an-instance |
Just FYI this bug (or something extremely similar!) has become substantially more severe in the past ~10 days (seemingly manifesting in new ways, e.g. known-to-be-reliable Ubuntu instances often-and-intermittently cannot boot). I don't know why. Certainly known-to-be-reliable Multipass instances (e.g. Ubuntu 22.04, Ubuntu 23.04 pre-releases, and others) frequently fail to start. FYI the Host PC is Ubuntu Server 22.04. The only workaround I've found so far is to repeatedly reboot the Host PC (rebooting it twice is sometimes necessary) until the Multipass instance in question...finally boots cleanly. CLARIF 1: Running CLARIF 2: I just reverted from Multipass's "edge" channel (1.12.x) to its "beta" channel (1.11.1) to see if that might somewhat help going forward?
|
Describe the bug
When using the LXD backend, after a failed launch where the instance gets into an error state (112 from LXD, translated to unknown in multipass), multipass is unable to delete the instance:
We would need to give LXD the equivalent of the
--force
flag in such cases.To Reproduce
Because of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935880 , a pretty reliable way to get a LXD vm in error state is just
multipass launch --cpus 2
multipass delete --purge <instance>
then fails as aboveExpected behavior
Multipass would be able to delete the instance.
The text was updated successfully, but these errors were encountered: