hashicorp / vagrant

Vagrant is a tool for building and distributing development environments.
https://www.vagrantup.com
Other
26.25k stars 4.43k forks source link

vagrant removes NFS exports for other users even though they're still in use #9070

Open NHellFire opened 7 years ago

NHellFire commented 7 years ago

Vagrant 2.0.0 (logs are from 1.9.8, 2.0.0 fails for the same reason) Host: Ubuntu 17.04

From the log, the exports checking always uses the current UID, so will always see other users' exports as no longer needed.

start as jenkins (guest is Ubuntu 17.04) log /etc/exports only contains this one like it should:

# VAGRANT-BEGIN: 1001 78806be8-d853-418e-a185-c27ea2cc67eb
"/home/jenkins/zmninja" 192.168.121.173(rw,no_subtree_check,all_squash,anonuid=1001,anongid=1001,fsid=4228835102)
# VAGRANT-END: 1001 78806be8-d853-418e-a185-c27ea2cc67eb

then start a different box as administrator, while the other one is still running (guest is jessie64) log the previous one is pruned, then /etc/exports only contains the new one:

# VAGRANT-BEGIN: 1000 630bcba6-0e8f-4e0b-bb90-ac4b0f92ee71
"/home/administrator/vagrant-test" 192.168.121.176(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=2695266041)
# VAGRANT-END: 1000 630bcba6-0e8f-4e0b-bb90-ac4b0f92ee71
chrisroberts commented 6 years ago

Hi @NHellFire. This is currently a known issue that we have scheduled to address in the near-term future. Thank you for the report.

kotsis commented 1 year ago

Hello I face the same issue. Just created a PR https://github.com/hashicorp/vagrant/pull/13112