Open JoelProminic opened 1 year ago
This looks like a problem with how "vagrant up" is called, but I don't see an immediate obvious problem: https://github.com/Moonshine-IDE/Super.Human.Installer/blob/76505210c85e11c95e87934d3a4d2e7592653b55/Source/superhuman/server/Server.hx#L1033 https://github.com/Moonshine-IDE/Super.Human.Installer/blob/76505210c85e11c95e87934d3a4d2e7592653b55/Genesis/Source/prominic/sys/applications/hashicorp/Vagrant.hx#L427
3. Delete the Vagrant instance
What do you mean by delete vagrant instance ? Did you go to Virtual Box and deleted it with files ?
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:
I updated the description with some more screenshots and notes
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.
Describe the bug
I have been seeing an error when recreating a Vagrant Server instance.
To Reproduce Steps to reproduce the behavior:
Desktop (please complete the following information):