Error when Recreating Server

[JoelProminic]

Describe the bug

I have been seeing an error when recreating a Vagrant Server instance.

To Reproduce
Steps to reproduce the behavior:

1. Already have a server created
2. Stop the server
3. Delete the Vagrant/VirtualBox instance:
   
4. Click the play button to create the server again
   
5. BUG: Server creation fails with:
   

The machine with the name 'd8fd4ea' was not found configured for the Vagrant environment.
[SHI]: 'vagrant up' stopped with exit code: 1, elapsed time 00:00:01

7. Restart SHI
8. Click the play button. This time it starts properly. I the only UI difference I see is that the third icon does not show the green dot after the restart:
   
   

Desktop (please complete the following information):

• OS: macOS
• Version: 12.6.5 Monterey, x86_64
• Vagrant 2.3.4
• Virtualbox 7.0.8

[JoelProminic]

This looks like a problem with how "vagrant up" is called, but I don't see an immediate obvious problem:

Super.Human.Installer/Source/superhuman/server/Server.hx

Line 1033 in 7650521

function _startVagrantUp() {

Super.Human.Installer/Genesis/Source/prominic/sys/applications/hashicorp/Vagrant.hx

Line 427 in 7650521

public function getUp( machine:VagrantMachine, ?provision:Bool = false, ?args:Array<String> ):AbstractExecutor {

[piotrzarzycki21]

3. Delete the Vagrant instance

What do you mean by delete vagrant instance ? Did you go to Virtual Box and deleted it with files ?

[JoelProminic]

Sorry, I meant to add some further clarification to this point. I mean that I used this button in SHI to delete the VirtualBox VM. I did not fully delete the server from SHI:

[JoelProminic]

I updated the description with some more screenshots and notes

[JoelProminic]

This may be a separate issue, but I'm also seeing cases where server is in a "stopped" state, but I don't see the red 'x' button. I think this maybe related to when the provisioning fails.:

% vagrant status
Current machine states:

6904--domino-1.demoprod.com poweroff (virtualbox)

The VM is powered off. To restart the VM, simply run `vagrant up`

The SHI state persists even if I restart SHI, in this case.

I was debugging some new problems with provisioning, and I had to restart SHI a bunch of times trying to work around the above bugs.