Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39740 - [vagrant] Crash when destroy or up boxes

Attached to Project: Community Packages
Opened by Pablo Serrano (Pserr) - Friday, 04 April 2014, 09:59 GMT
Last edited by Jonathan Steel (jsteel) - Tuesday, 08 April 2014, 16:54 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jonathan Steel (jsteel)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Vagrant Crash when destroy or up boxes

Additional info:
* package version : vagrant-1.5.2-1

Steps to reproduce: When destroy or up one or multiples box vagrant print this error message and don't working

vagrant destroy -f
/opt/vagrant/embedded/gems/gems/vagrant-1.5.2/plugins/kernel_v2/config/vm.rb:581:in `block in validate': undefined method `to_sym' for nil:NilClass (NoMethodError)
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/plugins/kernel_v2/config/vm.rb:552:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/plugins/kernel_v2/config/vm.rb:552:in `validate'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/config/v2/root.rb:68:in `block in validate'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/config/v2/root.rb:64:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/config/v2/root.rb:64:in `validate'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builtin/config_validate.rb:15:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builtin/call.rb:51:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builtin/call.rb:51:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/machine.rb:157:in `action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/plugins/commands/destroy/command.rb:30:in `block in execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/plugin/v2/command.rb:200:in `block in with_target_vms'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/plugin/v2/command.rb:194:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/plugin/v2/command.rb:194:in `with_target_vms'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/plugins/commands/destroy/command.rb:29:in `execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/cli.rb:42:in `execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/environment.rb:248:in `cli'
from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.5.2/bin/vagrant:158:in `<main>'
This task depends upon

Closed by  Jonathan Steel (jsteel)
Tuesday, 08 April 2014, 16:54 GMT
Reason for closing:  Upstream
Additional comments about closing:  Fixed with upstream's re-release of 1.5.2 (our 1.5.2-2)
Comment by Jeroen van den Heuvel (jeroenvdheuvel) - Friday, 04 April 2014, 11:13 GMT
Although not stated in the documentation of Vagrant, the network type is required since version 1.5.2.

As an example:
config.vm.network "private_network", ip: "192.168.50.4", type: "static"

Issue in Github is already created by somebody else: https://github.com/mitchellh/vagrant/issues/3387
When specifying any type (dhcp or anything else) the box seems to work.
Comment by Pablo Serrano (Pserr) - Friday, 04 April 2014, 11:30 GMT
Jeroen,

I'm testing on previous versions and it works also. Now i must change all my vagrantfile for all projects that i'm developing :S

Many thanks
Comment by Jeroen van den Heuvel (jeroenvdheuvel) - Friday, 04 April 2014, 11:32 GMT
I'm not sure if this will be fixed in the next version. For now best is probably to add the type, so at least the boxes will start again.
Comment by Pablo Serrano (Pserr) - Friday, 04 April 2014, 11:38 GMT
Yeah, all box running and destroy fine with add type. And how it's works with previous versions, nothings matters :)
Comment by Doug Newgard (Scimmia) - Friday, 04 April 2014, 15:19 GMT
Looks like they're re-releasing 1.5.2 to fix this.
Comment by Jonathan Steel (jsteel) - Friday, 04 April 2014, 19:31 GMT
Can someone rebuild from abs (I don't have access to my main computer right now) and see if the issue does "go away" (as suggested on the github link above)?
Comment by Bartłomiej Piotrowski (Barthalion) - Saturday, 05 April 2014, 17:51 GMT
They are or they did? The v1.5.2 tag point to the same commit as before.
Comment by Jonathan Steel (jsteel) - Sunday, 06 April 2014, 09:09 GMT
They took a while updating the tarball. 1.5.2 now has a new tag and md5sum. Pushing 1.5.2-2 now.
Comment by Jonathan Steel (jsteel) - Monday, 07 April 2014, 19:43 GMT
Is this particular issue resolved with 1.5.2-2? I can "up" and "destroy" boxes with 1.5.2-1 so I cannot confirm. Thanks.
Comment by Bartłomiej Piotrowski (Barthalion) - Tuesday, 08 April 2014, 10:22 GMT
Seems to be fine now. Thanks!

Loading...