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.

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

Error if hostmanager configuration option missing in Vagrantfile. My suggest => consider as enable=false #26

Closed
harobed opened this issue Jul 11, 2013 · 4 comments

Comments

@harobed
Copy link

harobed commented Jul 11, 2013

Hi,

if vagrant-hostmanager is installed and I haven't config.hostmanager.enabled present in my Vagrantfile, then I've this error :

Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

HostManager configuration:
* A value for hostmanager.enabled can only be true or false, not type 'Object'
* A value for hostmanager.manage_host can only be true or false, not type 'Object'
* A value for hostmanager.ignore_private_ip can only be true or false, not type 'Object'
* A value for hostmanager.include_offline can only be true or false, not type 'Object'

This is my Vagrantfile content :

Vagrant.configure("2") do |config|
  config.vm.box = "debian-wheezy64"
end

This is my plugin list :

$ vagrant plugin list
vagrant-cachier (0.1.0)
vagrant-hostmanager (1.0.1)
vagrant-hostsupdater (0.0.9)

Vagrant version : 1.2.2

My suggestion : consider hostmanager.enabled missing like hostmanager.enabled=false

What do you think about my suggest ?

Best regards,
Stéphane

@harobed
Copy link
Author

harobed commented Jul 11, 2013

Pull request here : #27

smdahlen added a commit that referenced this issue Jul 19, 2013
This commits adds a check in the config validation to allow for
UNSET_VALUE for boolean attributes. This is required when finalize is
not executed.
@smdahlen
Copy link
Contributor

@harobed I just posted a fix and published it as version 1.0.2. Could you please confirm?

@harobed
Copy link
Author

harobed commented Jul 19, 2013

Yes, fixed :)

@smdahlen
Copy link
Contributor

Thanks for checking. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants