We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have encountered an issue that appears to be intermittent in nature with vagrant up --provider=vsphere and multi-machine configuration.
Here are some details plus a link to a gist for files.
vagrant version 1.7.2 vagrant-vsphere version 1.0.1 vsphere version 5.5.0 guest OS is CentOS 6.4.
Just after 'Setting hostname...' is posted to stdout I receive an error which stops the rest of the vagrant machines from being started.
ERROR: INFO interface: Machine: error-exit ["VagrantPlugins::VSphere::Errors::VSphereError", "undefined method `[]' for nil:NilClass"]
Gist: https://gist.github.com/jreslock/a3b1ba8e3f9cc6c1af3b
I cross posted this because I don't know if it is a plugin issue or a core vagrant issue. What else can I do to debug this further?
The text was updated successfully, but these errors were encountered:
I was able to resolve/work around this error by reverting from vagrant 1.7.2 to vagrant 1.6.4.
Sorry, something went wrong.
I'm running vagrant 1.6.5 and I have the same issue. Please fix.
Hi @jreslock
Thank you for opening an issue. According to the debug log, this is an issue with the vagrant-vsphere plugin:
ERROR vagrant: #<VagrantPlugins::VSphere::Errors::VSphereError: undefined method `[]' for nil:NilClass>
I believe this is an issue with the vagrant-vsphere plugin 😄. Please open an issue on that repository.
For reference, the new issue has been reported in the vagrant-vsphere repository here.
No branches or pull requests
I have encountered an issue that appears to be intermittent in nature with vagrant up --provider=vsphere and multi-machine configuration.
Here are some details plus a link to a gist for files.
vagrant version 1.7.2
vagrant-vsphere version 1.0.1
vsphere version 5.5.0
guest OS is CentOS 6.4.
Just after 'Setting hostname...' is posted to stdout I receive an error which stops the rest of the vagrant machines from being started.
Gist: https://gist.github.com/jreslock/a3b1ba8e3f9cc6c1af3b
I cross posted this because I don't know if it is a plugin issue or a core vagrant issue. What else can I do to debug this further?
The text was updated successfully, but these errors were encountered: