Package: vagrant
Version: 1.4.3
Steps to reproduce:
Run debian unstable, date aug 13, 2014
apt-get update
apt-get dist-upgrade
apt-get install vagrant virtualbox
vagrant plugin install vagrant-omnibus
cd to location of Vagrantfile (contents of file listed below)
vagrant up
Resulting error:
The plugin "vagrant-omnibus" could not be found. Please make sure that it is
properly installed via `vagrant plugin`. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use `plugin install` with a 1.0.x plugin.
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:
Vagrant:
* Unknown configuration section 'omnibus'
Expected behavior:
No errors, vagrant loads a new instance with a virtualbox gui as
it's configured to do.
Other notes:
This behavior can be replicated with other plugins. I also tested
vagrant-berkshelf
Behavior is correct on ubuntu saucy, due to ruby 1.9.1 being default
(versions of all packages are older)
Note that Vagrantfile contents have no impact on the first component
of the error message, only the
second. e.g. removing the "omnibus" reference only reemoves the
"Unknown configuration
section 'omnibus'" error
Known woarkaround:
apt-get remove vagrant
Download version 1.6.3 as a .deb from the web
install it
Everything works flawlesslly
Suggested resolution:
Ruby versions are not forward compatible, as a result vagrant should depend
on a specific ruby version. ruby versions *are* slotted, so this should work
fine. e.g. vagrant 1.4.3 should probably depend on ruby 1.9.3
for an immediate fix upgrading to vagrant 1.6.3 would resolve this specific
instance of the more general problem.
Kernel version:
Linux slate 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 GNU/Linux
Vagrantfile contents follow:
# -*- mode: ruby -*-
# vi: set ft=ruby :
ARCH = 64
CHEF_VERSION = "11.10.4"
OS = "ubuntu"
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "base"
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
suffix = (ARCH == 32 ? '-i386' : '')
# Chef 11 support with opscode bento
config.vm.box = "opscode_ubuntu-14.04#{suffix}_chef-provisionerless"
config.vm.box_url =
"https://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-14.04#{suffix}_chef-provisionerless.box";
config.omnibus.chef_version = CHEF_VERSION
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network :forwarded_port, guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
config.vm.network :private_network, ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network :public_network
# If true, then any SSH connections made will enable agent forwarding.
# Default value: false
# config.ssh.forward_agent = true
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
config.vm.provider :virtualbox do |vb|
# # Don't boot with headless mode
vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
vb.customize ["modifyvm", :id, "--memory", "1024"]
end
#
# View the documentation for the provider you're using for more
# information on available options.
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file base.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
# config.vm.provision :puppet do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "site.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
config.vm.provision :chef_solo do |chef|
chef.cookbooks_path = "."
chef.add_recipe "base_machine"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME";
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
- Brewer
