haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Set uuid directly if VM couldn't be found. [GH-725] 

This fixes a rare edge case where an exception could actually cause
Vagrant to remove the UUID state of a running VM, "losing" it.
This commit is contained in:
Mitchell Hashimoto 2012-02-13 17:39:18 -08:00
parent 888907de91
commit 2cf146cf6b
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG.md
View File

@ -17,6 +17,8 @@
- Unix-style line endings are used properly for guest OS. [GH-727] - Unix-style line endings are used properly for guest OS. [GH-727]
- Retry certain VirtualBox operations, since they intermittently fail. - Retry certain VirtualBox operations, since they intermittently fail.
[GH-726] [GH-726]
- Fix issue where Vagrant would sometimes "lose" a VM if an exception
occurred. [GH-725]
## 0.9.7 (February 9, 2012) ## 0.9.7 (February 9, 2012)

2
lib/vagrant/vm.rb
View File

@ -131,7 +131,7 @@ module Vagrant
# Clear the UUID since this VM doesn't exist. Note that this calls # Clear the UUID since this VM doesn't exist. Note that this calls
# back into `reload!` but shouldn't ever result in infinite # back into `reload!` but shouldn't ever result in infinite
# recursion since `@uuid` will be nil. # recursion since `@uuid` will be nil.
self.uuid = nil @uuid = nil
end end
end end