Vagrant Update Message Triggers Incomplete Error

[JoelProminic]

Testing on macOS Monterey today with development build v0.8.18, I saw that provisioning finished like this:

The home page didn't open, and SHI reported: "Running with errors..."

Checking the output, I see failed=0 and stopped with exit code: 0, so there doesn't seem to be a problem. I want to revisit if we can determine if there are errors based on the exit code, instead of STDERR. I don't remember if there were other cases that required us to use STDERR, though.

I don't think this will prevent me from using the VM, but I'll update the issue if I run into more problems. The obvious solution is to update Vagrant, but this is still something that could trigger for us during normal use. There could also be cases where we can't update to the latest Vagrant version because of compatibility issues (I have seen this before with other projects).

UPDATE: I have been fighting with some network issues for new VMs, and I don't remember if this started before or after I updated to Vagrant 2.3.7. I recommend that you don't update Vagrant for the moment.

[JoelProminic]

This behavior doesn't make sense, and I haven't seen it trigger again. If this triggers again we can revisit this issue.