The offender is:
/usr/share/vagrant/plugins/guests/redhat/cap/nfs_client.rb

The code reads
 9             when :rhel_7
10               comm.sudo("/bin/systemctl restart rpcbind nfs")
11             else
12               comm.sudo("/etc/init.d/rpcbind restart; /etc/init.d/nfs restart")
13             end

I am also seeing issues with nfs shared folders.
But I think we need more details.

What exactly is the guest you are using?

I am having issues (with different messages) with
the fedora 22 cloud images as guest.

vagrant up died with:

~~~~~~~~~~~~~~~~~~~~~~~~~~
==> server: Installing NFS client...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/etc/init.d/rpcbind restart; /etc/init.d/nfs restart

Stdout from the command:



Stderr from the command:

bash: line 2: /etc/init.d/rpcbind: No such file or directory
bash: line 2: /etc/init.d/nfs: No such file or directory
~~~~~~~~~~~~~~~~~~~~~~~~~~

I'm not sure if I've gotten to the bottom of my issues with NFS, though, but the above seems like a clear bug..

Jakub:

What's your guest (box)?

Fedora-22.

I defined the guest as:

~~~~~~~~~~~~~~~~~
FREEIPA_SRC="/home/remote/jhrozek/devel/freeipa"

Vagrant.configure(2) do |config|
  config.vm.box = "fedora-22"
  config.vm.box_url = "http://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-libvirt.box"

  config.vm.define "server" do |server|
      server.vm.network "private_network", ip: "#{IP_ADDRESS}"
      server.vm.hostname = "#{HOSTNAME}"

      server.vm.synced_folder "#{FREEIPA_SRC}", "/freeipa", type: "nfs"

      server.vm.provider :libvirt do |domain|
          domain.memory = 1024
      end
  end                        
~~~~~~~~~~~~~~~~~

now that is strange - i use the same box and am not seeing this error msg. need to investigate...

btw I'm using stock Fedora vagrant on a F-21 *host*, maybe that makes some difference?

I only checked the upstream baseline for vagrant is the same, the F-22 changelog only says;

~~~~~~~
* Thu May 21 2015 Josef Stribny <jstribny> - 1.7.2-6
- Fix: Support new Fedora releases
- Fix: Don't try to use biosdevname if it's not installed
~~~~~~~

I just fixed the nfs_client.rb file to call systemctl always since I don't use RHEL-6 or older with vagrant, so I'm pretty happy now. I saw some strangeness with the NFS mounts once where I had to start rpc-statd manually, but couldn't reproduce it again..

So this issue doesn't really block me in any way..

Ok. My host is f22 with vagrant distro packages and the same vagrant box image.
That may explain differences in behaviour.

But I don't quite see yet how you are running into the rhel other than 7 branch in the rhel guest code with fedora. Well ...

The problem is that capabilities are inherited in this case from Red Hat's ones.
This should be fixed upstream by https://github.com/mitchellh/vagrant/commit/efd7b459dd999ef3177cb519d6beb809bb4e4d93.

Taking.

Apparently the new capabilities merged are not enough. I already submitted the fix upstream[0] and I will prepare fixes for Fedora 21 and 22.


[0] https://github.com/mitchellh/vagrant/pull/5859

(In reply to Josef Stribny from comment #10)
> Taking.
> 
> Apparently the new capabilities merged are not enough. I already submitted
> the fix upstream[0] and I will prepare fixes for Fedora 21 and 22.
> 
> 
> [0] https://github.com/mitchellh/vagrant/pull/5859

Thanks a lot, feel free to toss any test builds my way, I'll be glad to throw away mu current crude workarounds :)

Jakub,

it seemed the my fix was fixing only a scenario when the nfs-utils package wasn't installed. I rewrote my patch to handle both scenarios[0]. Now I can truly do the builds! :)


[0] https://github.com/mitchellh/vagrant/pull/5880

vagrant-1.7.2-8.fc21.1 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/vagrant-1.7.2-8.fc21.1

vagrant-1.7.2-8.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/vagrant-1.7.2-8.fc22

Package vagrant-1.7.2-8.fc21.1:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing vagrant-1.7.2-8.fc21.1'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-10996/vagrant-1.7.2-8.fc21.1
then log in and leave karma (feedback).

vagrant-1.7.2-8.fc21.1 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

vagrant-1.7.2-8.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.