-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
vagrant package fails on undefined method 'join' #5070
Comments
BTW I am using VirtualBox provider with VirtualBox 4.3.20 r96996 |
Also, I patched machine.rb with itaruru's fix from: |
The problem reproduced on MacOS X [10.9.5] with Vagrant 1.7.1 and patch from #4962. Any workaround for this? |
Backed out #4962, applied #4972. |
iam using ubuntu 14 and vagrant 1.7.1 which results in the same problem. i also tried installing from the github with vagrant 1.7.2 dev version which results in the last error almarco had: https://gist.github.com/almacro/aa0b74cd2207c1770dd2 |
Fixed in master, 1.7.2 coming out soon. |
I have this error in 1.7.2 . Is this fixed for anyone else?
|
Same error as above, running Vagrant 1.7.2, Mac Yosemite and Virtualbox 4.3.20 |
Same error as above for me, Vagrant 1.7.2 Mac Yosemite and Virtualbox 4.3.20 |
This has blocked me as well. Same error as above on Ubuntu 14.10 LTS, Vagrant 1.7.2 and Virtualbox 4.3.20 #5310 |
Same issue for me using Win7 Pro, Vagrant 1.7.2, VBox 4.3.20.. |
This should be re-opened as it isn't fixed in 1.7.2 and VirtualBox 4.3.20 (Fedora 21) |
Workaround for vagrant 1.7.2 : Test OK : |
@cdelaitre thanks for that! Working here as well with that change. CC: @mitchellh |
@cdelaitre Worked for me too. Thanks a lot. Also to @mitchellh, hoping that this will be fixed in the next version. ;) |
@cdelaitre many thanks - we had the same problem and this sorted it for us, just updated moments ago to see if this has been fixed yet but 1.7.2 is still the current. |
@cdelaitre Thanks dude, That work around helped me out too. |
@cdelaitre Thanks from me too. I'm new to Vagrant and your fix got me past a confusing and frustrating problem. |
@cdelaitre Thanks! works great! |
Same issue arose for me in Vagrant 1.7.3, thanks to @cdelaitre his workaround is exactly what it needed. |
Same issue arose for me in Vagrant 1.7.4, thanks to @cdelaitre his workaround is exactly what it needed. Thank also SAN1TAR1UM for providing my answer :) |
happens to me on 1.7.4 but #5070 (comment) above fixes it. |
I'm curious why this issue remains closed when several commenters report it is still occurring. Ditto for myself on v1.7.4, and for workaround from @cdelaitre. |
I was on vbox 5. In vbox 4.3 no issue |
I can confirm that this is still happening in version 1.7.4 on OS X 10.10.5 and VirtualBox version 4.3.30, and that the fix proposed by @cdelaitre works for me. |
1.7.4 on Windows 10 Pro and the bug is present. @cdelaitre's proposed fix helped. Why has this fix not made it in? It's been two versions since. |
The bug is still present in Vagrant 1.7.4 on Mac OSX 10.10.5. The fix proposed by @cdelaitre works and should be present in the next version of Vagrant. |
is still happening in 1.7.2 on Ubuntu 12.04 with VirtualBox 4.3.30, the fix from @cdelaitre works also for me, thanks |
Issue happens on Windows 10, Vagrant 1.7.2, Virtualbox 5.0.4. @cdelaitre fix works. |
We are on version 1.7.4 now, and the problem remains.
|
VirtualBox 4.3.28 It happened when the VM was still running. After I manually shutdown the VM with |
@mitchellh Please re-open this, you said it was fixed on 1.7.2 and here you can see people on 1.7.2, 1.7.3 and 1.7.4 STILL with this issue! |
Isn't this worth a 1.7.4.1 or something? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi There:
I hit breakage when running vagrant package using 1.7.1.
The output log is here: https://gist.github.com/almacro/485fd31916e64921b9a5
Here are some system fingerprints:
$ vagrant --version
Vagrant 1.7.1
$ ruby -v
ruby 2.0.0p353 (2013-11-22) [x86_64-linux]
$ uname -a
Linux localhost.localdomain 3.10.0-123.9.3.el7.x86_64 #1 SMP Thu Nov 6 15:06:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/centos-release
CentOS Linux release 7.0.1406 (Core)
The text was updated successfully, but these errors were encountered: