use rbvmomi at v1.11.5 and greater

v1.11.5 fixes the issue introduced in v1.11.4

vmware-archive/rbvmomi#127 (comment)

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 1.13.1
+current_version = 1.13.2
 tag = true
 commit = true
 

CHANGELOG.md

@@ -1,4 +1,9 @@
-## [1.13.1 (2017-12-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.0)
+## [1.13.2 (2017-12-06)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.2)
+
+  - Update rbvmomi dependency to v1.11.5 and greater (but still less than
+    2.0). v1.11.5 fixes the issue introduced in v1.11.4.
+
+## [1.13.1 (2017-12-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.1)
 
   - Update rbvmomi dependency to avoid v1.11.4; something in
     [2725089](https://github.com/vmware/rbvmomi/commit/2725089a08312315c4eb85f13296fc159f50b4d1)

README.md

@@ -19,9 +19,9 @@ This provider is built on top of the
 * libxml2, libxml2-dev, libxslt, libxslt-dev
 
 ## Current Version
-**version: 1.13.1**
+**version: 1.13.2**
 
-vagrant-vsphere (**version: 1.13.1**) is available from
+vagrant-vsphere (**version: 1.13.2**) is available from
 [RubyGems.org](https://rubygems.org/gems/vagrant-vsphere)
 
 ## Installation

lib/vSphere/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module VSphere
-    VERSION = '1.13.1'
+    VERSION = '1.13.2'
   end
 end

vSphere.gemspec

@@ -14,12 +14,7 @@ Gem::Specification.new do |s|
   # force the use of Nokogiri 1.5.x to prevent conflicts with older versions of zlib
   s.add_dependency 'nokogiri', '~>1.5'
 
-  # force the use of at least rbvmomi 1.8.2 to work around concurrency errors:
-  # https://github.com/nsidc/vagrant-vsphere/issues/139
-  #
-  # rbvmomi v1.11.4 broke cloning VMs at NSIDC, see
-  # https://github.com/vmware/rbvmomi/issues/127
-  s.add_dependency 'rbvmomi', '>=1.8.2', '<1.11.4'
+  s.add_dependency 'rbvmomi', '>=1.11.5', '<2.0.0'
 
   s.add_dependency 'i18n', '>=0.6.4', '<=0.8.0'