Problem running multiple vm's

I think there might be a problem when running multiple vm's. I got an ssh error when I tried to vagrant up doppler, and after that the same error also occured on provisioning of the develop machine. In the end I removed nersc-vagrant and reinstalled virtualbox, ansible and vagrant before I got it running again. Making a note of it here, so we remember...

This is the error I got:

GATHERING FACTS *************************************************************** 
<192.168.33.14> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.33.14> REMOTE_MODULE setup
<192.168.33.14> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o IdentityFile=/Users/mortenh/nersc-vagrant/.vagrant/machines/doppler/virtualbox/private_key -o ForwardAgent=yes -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/Users/mortenh/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 192.168.33.14 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1451648966.9-262457766527148 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1451648966.9-262457766527148 && echo $HOME/.ansible/tmp/ansible-tmp-1451648966.9-262457766527148'
fatal: [192.168.33.14] => SSH Error: ssh: connect to host 192.168.33.14 port 22: Operation timed out
    while connecting to 192.168.33.14:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.

nansencenter / nersc-vagrant

Problem running multiple vm's #11