Don't use rbvmomi v1.11.4

See vmware-archive/rbvmomi#127

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 1.13.0
+current_version = 1.13.1
 tag = true
 commit = true
 
@@ -8,4 +8,3 @@ commit = true
 [bumpversion:file:README.md]
 parse = version: (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)
 serialize = version: {major}.{minor}.{patch}
-

CHANGELOG.md

@@ -1,3 +1,10 @@
+## [1.13.1 (2017-12-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.0)
+
+  - Update rbvmomi dependency to avoid v1.11.4; something in
+    [2725089](https://github.com/vmware/rbvmomi/commit/2725089a08312315c4eb85f13296fc159f50b4d1)
+    broke cloning VMs on NSIDC's vSphere instance.
+
+
 ## [1.13.0 (2017-11-06)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.0)
 
   - Add support for the commands

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.0**
+**version: 1.13.1**
 
-vagrant-vsphere (**version: 1.13.0**) is available from
+vagrant-vsphere (**version: 1.13.1**) 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.0'
+    VERSION = '1.13.1'
   end
 end

vSphere.gemspec

@@ -13,9 +13,14 @@ 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
-  s.add_dependency 'rbvmomi', '>=1.8.2', '<2.0.0'
+  #
+  # 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 'i18n', '>=0.6.4', '<=0.8.0'
 
   s.add_development_dependency 'rake', '11.1.2' # pinned to accommodate rubocop 0.32.1