Last modified: 2014-11-17 21:36:04 UTC
Rarely VM could enter some "weird" unfinished state, for example if I hits Ctrl+C during "vagrant up", or if I do "vagrant halt" without "-f" followed immediately by "vagrant up" again. In that state, "vagrant up" causes a new machine to be created, even though the previous machine simply needs to be force-stopped. This causes lots of aggravation since I now have to re-attach proper VM to vagrant. I wrote about it in January 2013 at https://www.mediawiki.org/wiki/User:Yurik/Installing_Linux_virtual_box_under_Windows_7#Losing_VM_association -- how to restore that assoc, but I think our vagrant should be smart enough to warn users and/or attempt to force shutdown existing machine instead of creating a new one.
This sounds like an upstream bug for Vagrant rather than something we can or should fix in MediaWiki-Vagrant. Can we "won't fix" here or do you want to file upstream and track here?
Bulk unassigning bugs from Ori.