Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Fails to provision the VM #1

Closed
akhepcat opened this issue Sep 23, 2014 · 3 comments
Closed

Fails to provision the VM #1

akhepcat opened this issue Sep 23, 2014 · 3 comments

Comments

@akhepcat
Copy link

Just cloned the repo 90m ago, and can't get this to work:

$ VAGRANT_LOG=info vagrant  up
 INFO global: Vagrant version: 1.4.3
 INFO global: Ruby version: 1.9.3
 INFO global: RubyGems version: 1.8.23
 INFO global: VAGRANT_LOG="info"
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: VirtualBox provider
 INFO manager: Registered plugin: FreeBSD host
 INFO manager: Registered plugin: BSD host
 INFO manager: Registered plugin: Linux host
 INFO manager: Registered plugin: Red Hat host
 INFO manager: Registered plugin: OpenSUSE host
 INFO manager: Registered plugin: Arch host
 INFO manager: Registered plugin: Slackware host
 INFO manager: Registered plugin: Windows host
 INFO manager: Registered plugin: Gentoo host
 INFO manager: Registered plugin: ssh communicator
 INFO manager: Registered plugin: OpenBSD guest
 INFO manager: Registered plugin: Solaris guest.
 INFO manager: Registered plugin: CoreOS guest
 INFO manager: Registered plugin: FreeBSD guest
 INFO manager: Registered plugin: Linux guest.
 INFO manager: Registered plugin: Debian guest
 INFO manager: Registered plugin: Solaris 11 guest.
 INFO manager: Registered plugin: RedHat guest
 INFO manager: Registered plugin: Ubuntu guest
 INFO manager: Registered plugin: PLD Linux guest
 INFO manager: Registered plugin: OmniOS guest.
 INFO manager: Registered plugin: Fedora guest
 INFO manager: Registered plugin: ESXi guest.
 INFO manager: Registered plugin: Arch guest
 INFO manager: Registered plugin: Darwin guest
 INFO manager: Registered plugin: SUSE guest
 INFO manager: Registered plugin: Gentoo guest
 INFO manager: Registered plugin: help command
 INFO manager: Registered plugin: ssh-config command
 INFO manager: Registered plugin: suspend command
 INFO manager: Registered plugin: provision command
 INFO manager: Registered plugin: up command
 INFO manager: Registered plugin: plugin command
 INFO manager: Registered plugin: ssh command
 INFO manager: Registered plugin: halt command
 INFO manager: Registered plugin: reload command
 INFO manager: Registered plugin: init command
 INFO manager: Registered plugin: package command
 INFO manager: Registered plugin: status command
 INFO manager: Registered plugin: resume command
 INFO manager: Registered plugin: box command
 INFO manager: Registered plugin: destroy command
 INFO manager: Registered plugin: puppet
 INFO manager: Registered plugin: file
 INFO manager: Registered plugin: salt
 INFO manager: Registered plugin: CFEngine Provisioner
 INFO manager: Registered plugin: ansible
 INFO manager: Registered plugin: chef
 INFO manager: Registered plugin: docker
 INFO manager: Registered plugin: shell
 INFO manager: Registered plugin: NFS synced folders
 INFO vagrant: `vagrant` invoked: ["up"]
 INFO environment: Environment initialized (#<Vagrant::Environment:0x000000010f3ad8>)
 INFO environment:   - cwd: /usr/local/src/rpi-cross
 INFO environment: Home path: /home/leif/.vagrant.d
 INFO environment: Local data path: /usr/local/src/rpi-cross/.vagrant
 INFO environment: Running hook: environment_plugins_loaded
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000000013e0d40>
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "/usr/share/vagrant/config/default.rb"
 INFO loader: Set :root = #<Pathname:/usr/local/src/rpi-cross/Vagrantfile>
 INFO loader: Loading configuration in order: [:default, :home, :root]
 INFO hosts: Host class: VagrantPlugins::HostLinux::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000000014337c0>
 INFO cli: CLI: [] "up" ["--"]
 INFO environment: Getting machine: default (virtualbox)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
 INFO box_collection: Searching for box: ubuntu/trusty64 (virtualbox) in /home/leif/.vagrant.d/boxes/ubuntu/trusty64/virtualbox/metadata.json
 INFO box_collection: Searching for V1 box: ubuntu/trusty64
 INFO box_collection: Box not found: ubuntu/trusty64 (virtualbox)
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: VagrantPlugins::ProviderVirtualBox::Provider
 INFO machine:   - Box: 
 INFO machine:   - Data dir: /usr/local/src/rpi-cross/.vagrant/machines/default/virtualbox
 INFO base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
 INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_3
 INFO base: VBoxManage path: VBoxManage
 INFO command: With machine: default (VirtualBox (new VM))
 INFO interface: info: Bringing machine 'default' up with 'virtualbox' provider...
Bringing machine 'default' up with 'virtualbox' provider...
 INFO batch_action: Enabling parallelization by default.
 INFO batch_action: Disabling parallelization because provider doesn't support it: virtualbox
 INFO batch_action: Batch action will parallelize: false
 INFO batch_action: Starting action: #<Vagrant::Machine:0x000000014c5d28> up {:destroy_on_error=>true, :parallel=>true, :provision_ignore_sentinel=>false, :provision_types=>nil}
 INFO machine: Calling action: up on provider VirtualBox (new VM)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000000014b7b38>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x000000013bd570>
 INFO base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
 INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_3
 INFO base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "list", "hostonlyifs"]
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x000000013bd548>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000001473960>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::Created:0x00000001471f48>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Created:0x00000001471f48>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x000000014b0888>
 INFO warden: Calling IN action: #<Proc:0x0000000148dfb8@/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::HandleBoxUrl:0x000000014b06d0>
 INFO handle_box_url: Skipping HandleBoxUrl because box or box_url not set.
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::HandleBoxUrl:0x000000014b06d0>
 INFO warden: Calling OUT action: #<Proc:0x0000000148dfb8@/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x000000013bd4d0>
ERROR warden: Error occurred: There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'ubuntu/trusty64' could not be found.


 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000000013bd548>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Running hook: environment_unload
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000001454498>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::ConfigInvalid: There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'ubuntu/trusty64' could not be found.

>
ERROR vagrant: There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'ubuntu/trusty64' could not be found.


ERROR vagrant: /usr/lib/ruby/vendor_ruby/vagrant/action/builtin/config_validate.rb:18:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/builtin/call.rb:57:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/share/vagrant/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `block in run'
/usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `run'
/usr/lib/ruby/vendor_ruby/vagrant/machine.rb:147:in `action'
/usr/lib/ruby/vendor_ruby/vagrant/batch_action.rb:63:in `block (2 levels) in run'
 INFO interface: error: There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'ubuntu/trusty64' could not be found.


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

vm:
* The box 'ubuntu/trusty64' could not be found.
@tjanson
Copy link
Owner

tjanson commented Sep 23, 2014

Does this comment on a different project fix the issue? According to that, upgrading Vagrant to 1.5 solves the issue. I'm personally running the latest Vagrant (~1.6.5-ish).

Edit: the discussion of this issue (hopefully) at VVV has more info: apparently the shorthand notation was introduced in v1.5. So it's probably possible to add the full URL to the box like this, but I'd suggest upgrading to avoid further issues.

@akhepcat
Copy link
Author

Brilliant.

Upgraded to latest 1.6.5 (didn't quickly find a ppa) from the direct
site and now everything seems hunky-dory.

On 9/22/2014 4:32 PM, tjanson wrote:

Does this comment on a different project fix the issue
fideloper/Vaprobash#322 (comment)?
According to that, upgrading Vagrant to 1.5 solves the issue. I'm
personally running the latest Vagrant (~1.6.5-ish).


Reply to this email directly or view it on GitHub
#1 (comment).

@tjanson tjanson closed this as completed Sep 23, 2014
@tjanson
Copy link
Owner

tjanson commented Sep 23, 2014

Glad to hear. I'll add that to the instructions.

tjanson added a commit that referenced this issue Sep 23, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants