Closed JoelProminic closed 10 months ago
This may be a separate error, but I tried to recreate the VM, but I got an immediate error.
---- Hosts.yml END ----
[SHI]: VirtualBox VM: { serverId => 8699, virtualBoxId => 8699--demo.STARTcloud.com }
[SHI]: Executing 'vagrant up' (provision:false)
[SHI]: 'vagrant up' started
The machine with the name '938440b' was not found configured for
this Vagrant environment.
[SHI]: 'vagrant up' stopped with exit code: 1, elapsed time: 00:00:01
[SHI]: Server destroyed
I confirmed the VM did not exist. SHI showed this state:
I did not get an error on the Abort action (surprisingly), and "vagrant up" started properly on my next attempt.
I was talking with Josh and crash was happened in the main thread. It seems to be fixed with https://github.com/openfl/openfl/commit/ec633950121afdb22100773e61f0e3e905580d6d
I have tested it and couldn't reproduce this error.
This comment is covered by #92.
I have not seen the crash since my original report, but I did see these steps occasionally when I was testing with 0.8.19 over the last week.
This behavior was triggering when I was trying to recreate the server, similar to #92. After stopping the VM, SHI would end up in a state where I couldn't delete the VM, but the VM still existed. To fix this, I needed to manually run "vagrant destroy" and then rerun SHI.
If I see this trigger again after the 0.8.20 release, I'll create a separate issue. Unfortunately, this bug was triggering inconsistently, so I'm not sure how to reproduce it without just running multiple recreate tests.
I got a crash today with v0.8.16 Development on macOS Monterey when I tried to delete a VM:
My steps before this triggered: