For the record I installed the latest gem from source. It appears they fixed the issue with the error messages.
However it now appears that I am getting the following error: INFO warden: Calling IN action: #<Proc:0x00000100b90770@/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.3/lib/vagrant/action/warden.rb:94 (lambda)> INFO warden: Calling IN action: #<VagrantPlugins::VSphere::Action::Clone:0x00000100b6a688> INFO interface: info: Calling vSphere CloneVM with the following settings: INFO interface: info: ==> default: Calling vSphere CloneVM with the following settings: ==> default: Calling vSphere CloneVM with the following settings: INFO interface: info: -- Source VM: vagrantbase1 INFO interface: info: ==> default: -- Source VM: vagrantbase1 ==> default: -- Source VM: vagrantbase1 INFO interface: info: -- Name: default_1398362901196_65194 INFO interface: info: ==> default: -- Name: default_1398362901196_65194 ==> default: -- Name: default_1398362901196_65194 NotSupported: The operation is not supported on the object. ERROR warden: Error occurred: No error message INFO warden: Beginning recovery process... Anyone ever get the operation not supported error message? On Thursday, April 17, 2014 10:42:45 AM UTC-3, [email protected] wrote: > > Hi, > > I seem to be getting an error that is reporting as "No Error Message". For > the record I have tried different vagrant versions etc. For testing I am > using the root account on my test vsphere box. Using VMware ESXi and > vcenter, 5.5.0. > > I have confirmed that I am authenticating against vsphere fine. > > Just curious if anyone else has run into anything like this: > > https://github.com/nsidc/vagrant-vsphere/issues/53 > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
