Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Vagrant 1.7 doesn't read vSphere connection info from a base vagrant box #111

Merged
merged 1 commit into from
Dec 30, 2014
Merged

Vagrant 1.7 doesn't read vSphere connection info from a base vagrant box #111

merged 1 commit into from
Dec 30, 2014

Conversation

mkuzmin
Copy link
Contributor

@mkuzmin mkuzmin commented Dec 29, 2014

This PR fixes a Vagrant 1.7 compatibility issue.

Vagrant fails to start a machine when a vagrant box is downloaded from remote server, and local Vagrantfile doesn't contain vSphere connection info.

Error occurred: There are errors in the configuration of this machine. Please fix
the following errors and try again:

vSphere Provider:
* Configuration must specify a vSphere host
* Configuration must specify a vSphere user
* Configuration must specify a vSphere password
* Configuration must specify a template name
* Configuration must specify a compute resource name

The values are specified within a base vagrant box, but due to hashicorp/vagrant#4513 get_state action is now called earlier.

Fixed Vagrant 1.7 compatibility issue.
bbca64e 
Vagrant started to call get_state action inside 'vagrant up' command (hashicorp/vagrant#4513).
`vagrant up` fails with `There are errors in the configuration of this machine` error, if vagrant boxes are downloaded from remote server, and local Vagrantfile don't contain vSphere connection info.
@michaeljb michaeljb merged commit bbca64e into nsidc:master Dec 30, 2014
michaeljb added a commit that referenced this pull request Dec 30, 2014
@michaeljb
Update README for pull request #111
a144f48
@michaeljb
Copy link
Contributor

Thanks!

@mkuzmin mkuzmin deleted the get-state branch January 1, 2015 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@mkuzmin @michaeljb