-
-
Notifications
You must be signed in to change notification settings - Fork 641
undefined method
if using empty string/native synced folder with Vagrant 1.8.6
#912
Comments
This sounds like it is an upstream issue with Vagrant (issue queue: https://github.com/mitchellh/vagrant/issues). I haven't updated to 1.8.6 yet, but will soon, and I'll see if I get the same error. |
Think it might be the blank "type:"? 1.8.6 has been OK so far here. |
@joestewart - That could be it; @cdmo how do you have your shares/synced directories defined in config.yml? |
I was just reading over the documentation and noticed this same potential issue and changed it to |
I ran into this problem yesterday after upgrading Vagrant & VirtualBox. Could you please detail which ruby version you use, and how it was implemented on the system (even if it's the default setup). I use RVM and switching ruby versions fixed it for me. You could also try reinstalling ruby if you're using the system default ruby. |
To solve this right now, I just uninstalled Vagrant and reinstalled 1.8.5 and everything is working as expected for native shares. Thanks. |
Same issue here, Windows 10, Vagrant 1.8.6, VirtualBox 5.0.28 Tried updating Ruby from 2.2 to latest 2.3.1p112 (2016-04-26 revision 54768) [x64-mingw32 Downgraded vagrant back to 1.8.5 and its working You can view repo at: https://github.com/Stony-Brook-University/doitsbu/tree/master/vendor/geerlingguy/drupal-vm |
I have the same issue. Any possible solution other than downgrading? |
Right now, use either |
undefined method
, vagrant 1.8.6undefined method
if using empty string/native synced folder with Vagrant 1.8.6
nfs isn't available on non-enterprise Windows life is hell :( |
I'm fairly certain we could figure out a syntax fix for this that's not too difficult, it just hasn't been as high priority as keeping everything else running (latest Vagrant/VirtualBox updates threw a bunch of curveballs, and I'm still catching up there). If someone knows a little Ruby, it's probably a little syntax issue or something like double vs single quotes, who knows. |
To use virtualbox native shares you can also set |
I'm pretty sure this is the cause https://github.com/mitchellh/vagrant/pull/7720/files#diff-97d643b35101562477f4b556a379415fL30.
We should revert 5904e8e. |
TL;DR; Vagrant 1.8.4 caused an issue when As of 1.8.6 they changed the logic again and now mount_options = options.fetch(:mount_options, []) # evaluates to mount_options = nil
mount_options += ["uid=#{mount_uid}", "gid=#{mount_gid}"] |
…ers with empty mount_options
Could you test if the PR above works? |
@jelo77 / @Razunter / @sbubaron / @fubarhouse / @cdmo - Can you test the above PR? It looks to me like it should fix the issue, just want to confirm before merging. Then I'll be happy to tag a new bugfix release for Drupal VM so people can feel more comfy upgrading Vagrant too :) |
@geerlingguy it works. Tested with empty values. |
That indeed fixed this problem, but then the installer dies on the firewall ("Could not find the requested service 'firewall':"). Ansible failed to complete successfully. @Razunter did you not have this issue? |
@jelo77 no, machine just started without issues. |
@jelo77 - That was related to geerlingguy/ansible-role-firewall#17 (separate issue). Thanks for confirming the shared folder fix, I'll merge it and tag a bugfix release! |
Issue #912: Fix Vagrant 1.8.6 failing to mount synced folders with empty mount_options
Just want to chime in to share that changing Also, how did I remove the "question" label - I don't remember doing that. 🤔 |
@cdmo - That seems to be a GitHub issue... I removed the label, but it credited the change to you (the issue author). Go figure! |
…ers with empty mount_options
Just to write, this fixed it for me too, thanks! |
…ers with empty mount_options
Getting an
undefined method
error when using vagrant 1.8.6. I had a new developer join the team this week and she discovered it first. Then I upgraded from 1.8.5 to 1.8.6 and I hit the same error.Any ideas where this is coming from?
Using CentOS7, Drupal 7, native shares...
this is my config.yml: https://gist.github.com/cdmo/d22d6f9ebfd62f8df9f6263613d893a1
The text was updated successfully, but these errors were encountered: