It seems I am not the first to have this kind of problem but I do not see any answer to the problem in the discussion.
I am on a personal windows 10 lenovo P73.
I installed vagrant in march 2020 and used it on previous mongodb courses without problem. This install included minGW ssh and rsync. I do see them under C:\MinGW\msys\1.0\bin. This path is included in the windows PATH variable. Rsync and ssh do answer when called from cmd prompt.
I installed the vagrant-vbguest plugin without problem. It is listed when I ask for vagrant plugin list.
I corrected the provision-database file since the first attempt to start the database VM failed. It is now up and running (I destroyed then recreated the VM). I can connect to the database VM and it does show a mongo install.
I then tried several times to start the infrastructure VM and it always fails at the SSH connexion attempt and goes in timeout. I destroyed the infra VM and tried several times to start it but it still fails the same way. I rebooted windows, tried with database VM running and stopped (vagrant halt database) but I still have the same problem. Both VM are shown as running in the virtualbox interface but vagrant does not seems to be able to connect to the infrastructure one.
I note that there is a port collision mentioned during the infra start but it is noted as resolved (2222 => 2200). Indeed the ssh connexion that fails (timeout) is made to 127.0.0.1:2200. The port redirection is mentionned correctly in the virtualbox admin interface for network properties of infrastructure VM.
Here’s the error I see in vagrant :
Any idea ?