You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
==> default: Attempting graceful shutdown of VM...
==> default: Destroying VM and associated drives...
/usr/share/vagrant/gems/gems/vagrant-vbguest-0.32.0/lib/vagrant-vbguest/hosts/virtualbox.rb:84:in `block in guess_local_iso': undefined method `exists?' for class File (NoMethodError)
path && File.exists?(path)
^^^^^^^^
Expected behavior
Vagrant up bring up a vm
Actual behavior
vagrant fails bringing up a vm when is trying to update vbguest
Reproduction information
Vagrant version
Vagrant 2.3.7
Host operating system
opensuse tumbleweed VERSION=20240521
Guest operating system
Centos7 (a box of)
Steps to reproduce
So i fixed it by editing the file /usr/share/vagrant/gems/gems/vagrant-vbguest-0.32.0/lib/vagrant-vbguest/hosts/virtualbox.rb:
def guess_local_iso
Array(platform_path).find do |path|
- path && File.exists?(path)
+ path && File.exist?(path)
end
end
The NoMethodError give me the clue. And the ^^^^^ :-) Is easy to fix but it is annoying anyway.
Vagrantfile
# Copy-paste your Vagrantfile here. Remove any sensitive information such as passwords, authentication tokens, or email addresses.
The text was updated successfully, but these errors were encountered:
Debug output
Expected behavior
Vagrant up bring up a vm
Actual behavior
vagrant fails bringing up a vm when is trying to update vbguest
Reproduction information
Vagrant version
Vagrant 2.3.7
Host operating system
opensuse tumbleweed VERSION=20240521
Guest operating system
Centos7 (a box of)
Steps to reproduce
So i fixed it by editing the file /usr/share/vagrant/gems/gems/vagrant-vbguest-0.32.0/lib/vagrant-vbguest/hosts/virtualbox.rb:
The NoMethodError give me the clue. And the ^^^^^ :-) Is easy to fix but it is annoying anyway.
Vagrantfile
# Copy-paste your Vagrantfile here. Remove any sensitive information such as passwords, authentication tokens, or email addresses.
The text was updated successfully, but these errors were encountered: