NFS not mounting, INFO interface: Machine: error-exit ["Vagrant::Errors::NFSNoValidIds", "No valid IDs were given to the NFS synced folder implementation to\nprune. This is an internal bug with Vagrant and an issue should be\nfiled."]

[Herschdorfer]

I using vagrant 2.0.2 with the vagrant-winnfsd 1.4.0 on a Windows Hyper-V with a CentOS guest.
My vagrant file shows the following line:

config.vm.synced_folder "C:/shared", "/shared",
			create: "true",
			type: "nfs",
			nfs_verison: 3,
			nfs_host_ip: "10.0.0.1"

The vagrant output shows:

No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.

the folder is not mounted afterwards.

LOG debug:

==> default: Machine booted and ready!
 INFO warden: Calling IN action: #<VagrantPlugins::SyncedFolderNFS::ActionCleanup:0x00000000057d3b38>
 WARN nfs: nfs_valid_ids not set, cleanup cannot occur
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolderCleanup:0x000000000577acb8>
DEBUG host: Searching for cap: nfs_installed
DEBUG host: Checking in: windows
DEBUG host: Found cap: nfs_installed in windows
 INFO host: Execute capability: nfs_installed [#<Vagrant::Environment: C:/P/vagrant/box-CLN>] (windows)
DEBUG host: Searching for cap: nfs_installed
DEBUG host: Checking in: windows
DEBUG host: Found cap: nfs_installed in windows
 INFO host: Execute capability: nfs_installed [#<Vagrant::Environment: C:/P/vagrant/box-CLN>] (windows)
 INFO synced_folder_cleanup: Invoking synced folder cleanup for: nfs
ERROR warden: Error occurred: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<VagrantPlugins::ProxyConf::Action::OnlyOnce:0x0000000004007d38>
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000000000525b818>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
ERROR warden: Error occurred: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000004b3c1b8>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
ERROR warden: Error occurred: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000000043c8c10>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Released process lock: machine-action-3703ef2459541bb753fbbb52ccb93759
 INFO environment: Running hook: environment_unload
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 3 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00000000053ddc40>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::NFSNoValidIds: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.>
ERROR vagrant: No valid IDs were given to the NFS synced folder implementation to
prune. This is an internal bug with Vagrant and an issue should be
filed.
ERROR vagrant: C:/vagrant/embedded/gems/gems/vagrant-2.0.2/plugins/synced_folders/nfs/synced_folder.rb:118:in `cleanup'

[du365]

+1, same issue, any idea for it?

[Herschdorfer]

I was not able to solve this issue, I also tried downgrading (vagrant 1.9.x) but the error still persist.

[marcharding]

Please try to comply remove vagrant and than reinstall it. Does the error persist?

[Herschdorfer]

Yes I completely removed vagrant, downgraded to 1.9.x, removed again and installed 2.0.2.

Still no luck.

[marcharding]

I missed the hyper-v bit, hyper-v currently does not work, see #109

[marcharding]

Closing these, further discussion in #109