Description of problem: Following instruction from https://fedoraproject.org/wiki/Vagrant Create example Vagrantfile and run `vagrant up`: $ vagrant up Bringing machine 'default' up with 'libvirt' provider... /usr/share/vagrant/lib/vagrant/action/builtin/mixin_synced_folders.rb:137:in `block in synced_folders': Internal error. Report this as a bug. Invalid: sshfs (RuntimeError) from /usr/share/vagrant/lib/vagrant/action/builtin/mixin_synced_folders.rb:125:in `each' from /usr/share/vagrant/lib/vagrant/action/builtin/mixin_synced_folders.rb:125:in `synced_folders' from /usr/share/vagrant/lib/vagrant/action/builtin/synced_folder_cleanup.rb:19:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/action/set_boot_order.rb:60:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/action/create_networks.rb:80:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builtin/provision.rb:80:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:95:in `block in finalize_action' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builder.rb:116:in `call' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `block in run' from /usr/share/vagrant/lib/vagrant/util/busy.rb:19:in `busy' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `run' from /usr/share/vagrant/lib/vagrant/action/builtin/call.rb:53:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:95:in `block in finalize_action' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builder.rb:116:in `call' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `block in run' from /usr/share/vagrant/lib/vagrant/util/busy.rb:19:in `busy' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `run' from /usr/share/vagrant/lib/vagrant/action/builtin/call.rb:53:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builtin/config_validate.rb:25:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:95:in `block in finalize_action' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builder.rb:116:in `call' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `block in run' from /usr/share/vagrant/lib/vagrant/util/busy.rb:19:in `busy' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `run' from /usr/share/vagrant/lib/vagrant/action/builtin/call.rb:53:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builtin/config_validate.rb:25:in `call' from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call' from /usr/share/vagrant/lib/vagrant/action/builder.rb:116:in `call' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `block in run' from /usr/share/vagrant/lib/vagrant/util/busy.rb:19:in `busy' from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `run' from /usr/share/vagrant/lib/vagrant/machine.rb:225:in `action_raw' from /usr/share/vagrant/lib/vagrant/machine.rb:200:in `block in action' from /usr/share/vagrant/lib/vagrant/environment.rb:561:in `lock' from /usr/share/vagrant/lib/vagrant/machine.rb:186:in `call' from /usr/share/vagrant/lib/vagrant/machine.rb:186:in `action' from /usr/share/vagrant/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run' Version-Release number of selected component (if applicable): # rpm -qa 'vagrant*' vagrant-libvirt-doc-0.0.35-1.fc25.noarch vagrant-libvirt-0.0.35-1.fc25.noarch vagrant-1.8.5-2.fc25.noarch How reproducible: Always
It seams package vagrant-sshfs required
From the linked wiki page: "To get started with the above example, simply write the code to a file called Vagrantfile, install vagrant-libvirt and vagrant-sshfs, and run vagrant up"
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
I saw this error yesterday, and still reproducible. I'm working on Fedora 27 (4.13.11-300.fc27.x86_64), I did the install of vagrant-sshfs using `sudo dnf install vagrant-sshfs` and basically I followed the guide commented by Pavel Alexeev in the description, so when I did `vagrant up --provision=libvirt` the error was shown. To avoid that I removed vagrant-sshfs and some other packages that gave me problems and reinstalled appending --releasever=26 like `sudo dnf install vagrant-sshfs --releasever=26 -y` and it just worked that way for me.
(In reply to Alan Trevino from comment #4) > I saw this error yesterday, and still reproducible. > I'm working on Fedora 27 (4.13.11-300.fc27.x86_64), I did the install of > vagrant-sshfs using `sudo dnf install vagrant-sshfs` and basically I > followed the guide commented by Pavel Alexeev in the description, so when I > did `vagrant up --provision=libvirt` the error was shown. > > To avoid that I removed vagrant-sshfs and some other packages that gave me > problems and reinstalled appending --releasever=26 like `sudo dnf install > vagrant-sshfs --releasever=26 -y` and it just worked that way for me. Are you saying the version of vagrant-sshfs in f27 is bad?
(In reply to Dusty Mabe from comment #5) > (In reply to Alan Trevino from comment #4) > > I saw this error yesterday, and still reproducible. > > I'm working on Fedora 27 (4.13.11-300.fc27.x86_64), I did the install of > > vagrant-sshfs using `sudo dnf install vagrant-sshfs` and basically I > > followed the guide commented by Pavel Alexeev in the description, so when I > > did `vagrant up --provision=libvirt` the error was shown. > > > > To avoid that I removed vagrant-sshfs and some other packages that gave me > > problems and reinstalled appending --releasever=26 like `sudo dnf install > > vagrant-sshfs --releasever=26 -y` and it just worked that way for me. > > Are you saying the version of vagrant-sshfs in f27 is bad? Looks like it didn't work to me the way it should by installing directly `sudo dnf install vagrant-sshfs` the workaround I described is the way it worked (adding releasever=26). I'm not that sure if it's directly tied to the fact that the package doesn't get installed properly on f27 or the problem is that I'm using a beta to work and not all package had been properly setup in it. This is the package that I have installed at this point: vagrant-sshfs-1.3.0-3.fc26.noarch
For me (Fedora 27), the issue is resolved by simply reinstalling the vagrant-sshfs package (using the F26 version not necessary). I had a similar problem with the vagrant-libvirt support. It would fail until reinstalling that package, after which it would work fine.
But I should be clear - I was also experiencing this issue. It is reproducible for me as well on Fedora 27. The vagrant, vagrant-libvirt, and vagrant-sshfs packages were all present prior to attempting to "vagrant up" and it failed with the same message. As mentioned, it cleared up after "dnf reinstall vagrant-sshfs", despite the package already being installed. I've not looked into it but perhaps there is some fragile postinstall steps involved.
Daniel, Alan, I just opened a bug against the vagrant rpm for this: https://bugzilla.redhat.com/show_bug.cgi?id=1523296
There could be a better error message proposing to install `vagrant-sshfs` instead of failing with a traceback.
Again, a better error message about missing `vagrant-sshfs` would be more user friendly.
(In reply to Anatoli Babenia from comment #11) > Again, a better error message about missing `vagrant-sshfs` would be more > user friendly. This BZ is against the vagrant-sshfs package. If you want that functionality you'd need to open a feature against vagrant upstream (not vagrant-sshfs). It's impossible for the vagrant-sshfs software to print out a "better error message" if it's not even installed.
I missed that point. Thanks. Next time I fill it against `vagrant` itself.