VM Destroy Button Missing After Stopping VM

[JoelProminic]

While testing with Super.Human.Installer 0.8.20 and Development 0.8.21 on macOS Monterey and Ventura, I have noticed that in at least some cases I can't delete the VirtualBox VM after stopping a server:

I confirmed that the VirtualBox VM still exists:

% vagrant status
Current machine states:

7839--demo2.STARTcloud2.com poweroff (virtualbox)

Note that I have enabled "Do not stop/destroy servers that failed to start" in the Settings page, since I want to debug problems with the provisioners. In my above screenshot I see that the first VM shows "Stopped (provisioned)", while the second shows "Stopped" only. So, my suspicion is that this bug triggers when the "provisioned" tab is not set.

Steps to reproduce:

1. Create a new server
2. Run the server. This has usually been failing in my tests
3. Stop the VM
4. BUG: the delete button is not available once the state updates. I can delete the server, but this leaves the VirtualBox VM
5. Restart SHI. BUG: the delete button is still missing
6. Workaround: Open the directory in Terminal, and run "vagrant destroy". Restart SHI, and the server will be ready to be created again.

[piotrzarzycki21]

In second case 7839 - wasn't provisioned/started at all yes ? In that case Delete button is priovided (last one) which has nothing to do with stopping the server itself. Do you expect in second case to have red button for stopping server ? Does second case exists in Virtual Box ?

[JoelProminic]

Yes, I believe the demo2 VM was not successfully created, which is why it did not have the "provisioned" flag set. However, because I had enabled "Do not stop/destroy servers that failed to start", the VM was not stopped or deleted manually. I wanted to manually stop and destroy the VM so that I could rerun my test.