vagrant sync_folder not working sometimes after "vagrant reload"

y1y123 commented 4 years ago

Vagrant version

2.2.9

Host operating system

MAC OS Catalina 10.15.7

This is the operating system that you run locally.

Guest operating system

Cisco Nexus (variant of Linux)

Vagrantfile

config.vm.define "n9kv1" do |n9kv1|

    n9kv1.vm.box = "nexus9300v.9.4.1.IJB9.0.564.box"

    n9kv1.ssh.insert_key = false
    n9kv1.vm.boot_timeout = 600

    if Vagrant.has_plugin?("vagrant-vbguest")
      config.vbguest.auto_update = false
    end

    config.vm.box_check_update = false

end

Debug output

M-J0QM vagrant % vagrant reload --debug INFO global: Vagrant version: 2.2.9 INFO global: Ruby version: 2.6.6 INFO global: RubyGems version: 3.0.3 INFO global: VAGRANT_INSTALLER_VERSION="2" INFO global: VAGRANT_INSTALLER_ENV="1" INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded" INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/2.2.9/gems/vagrant-2.2.9/bin/vagrant" INFO global: VAGRANT_LOG="debug" DEBUG guest: Trying: linux ---- snip ---- DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: if test -r /etc/os-release; then source /etc/os-release && test 'xlinux' = "x$ID" && exit fi if test -x /usr/bin/lsb_release; then /usr/bin/lsb_release -i 2>/dev/null | grep -qi 'linux' && exit fi if test -r /etc/issue; then cat /etc/issue | grep -qi 'linux' && exit fi exit 1 (sudo=false) DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh DEBUG ssh: Exit status: 0 INFO guest: Detected: linux! DEBUG guest: Searching for cap: halt DEBUG guest: Checking in: linux DEBUG guest: Found cap: halt in linux INFO guest: Execute capability: halt [#<Vagrant::Machine: n9kv1 (VagrantPlugins::ProviderVirtualBox::Provider)>] (linux) DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: ps -o comm= 1 | grep systemd (sudo=true) DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh DEBUG ssh: Exit status: 1 DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: shutdown -h now (sudo=true) DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh DEBUG ssh: Sending SSH keep-alive... DEBUG ssh: Sending SSH keep-alive... DEBUG ssh: Sending SSH keep-alive... DEBUG ssh: Sending SSH keep-alive... DEBUG ssh: Sending SSH keep-alive... DEBUG ssh: Sending SSH keep-alive... DEBUG ssh: Sending SSH keep-alive... DEBUG ssh: Sending SSH keep-alive... --- snip --- Above logs keep repeating forever.

Expected behavior

Folder was correctly mounted with vagrant up and same should have worked after reload.

What should have happened?

Folder should have been mounted

Actual behavior

Vagrant is probably waiting for VM to come up even though after reload. I see that VM reloads when I issue "vagrant reload" command. I can do "vagrant ssh" and land to bash prompt but I do not see folder created and mounted in the guest VM.

What actually happened?

As mentioned above, "vagrant reload" commands reloads the VM but does not mount the folder.

Steps to reproduce

Please refer case and note that default shell is now bash, so file mount works fine with vagrant up. https://github.com/hashicorp/vagrant/issues/11762

References

https://github.com/hashicorp/vagrant/issues/11762

y1y123 commented 4 years ago

Update on issue above, the issue seems to be random, it works sometimes and sometimes get stuck as shown in logs above.

y1y123 commented 4 years ago

Stuck with following logs again. Even th

M-J0QM vagrant % vagrant reload
==> n9kv1: Attempting graceful shutdown of VM...

hashicorp / vagrant