providers/virtualbox: catch subprocess launch error [GH-1483]
This commit is contained in:
parent
28a42122b8
commit
36fa04fd1e
|
@ -75,6 +75,8 @@ BUG FIXES:
|
||||||
- providers/hyperv: only set EFI secure boot for gen 2 machines [GH-5538]
|
- providers/hyperv: only set EFI secure boot for gen 2 machines [GH-5538]
|
||||||
- providers/virtualbox: read netmask from dhcpservers [GH-5233]
|
- providers/virtualbox: read netmask from dhcpservers [GH-5233]
|
||||||
- providers/virtualbox: Fix exception when VirtualBox version is empty. [GH-5308]
|
- providers/virtualbox: Fix exception when VirtualBox version is empty. [GH-5308]
|
||||||
|
- providers/virtualbox: Fix exception when VBoxManage.exe can't be run
|
||||||
|
on Windows [GH-1483]
|
||||||
- provisioners/ansible: fix SSH settings to support more than 5 ssh keys [GH-5017]
|
- provisioners/ansible: fix SSH settings to support more than 5 ssh keys [GH-5017]
|
||||||
- provisioners/ansible: increase ansible connection timeout to 30 seconds [GH-5018]
|
- provisioners/ansible: increase ansible connection timeout to 30 seconds [GH-5018]
|
||||||
- provisioners/ansible: disable color if Vagrant is not colored [GH-5531, GH-5532]
|
- provisioners/ansible: disable color if Vagrant is not colored [GH-5531, GH-5532]
|
||||||
|
|
|
@ -720,6 +720,10 @@ module Vagrant
|
||||||
error_key(:vboxmanage_error)
|
error_key(:vboxmanage_error)
|
||||||
end
|
end
|
||||||
|
|
||||||
|
class VBoxManageLaunchError < VagrantError
|
||||||
|
error_key(:vboxmanage_launch_error)
|
||||||
|
end
|
||||||
|
|
||||||
class VBoxManageNotFoundError < VagrantError
|
class VBoxManageNotFoundError < VagrantError
|
||||||
error_key(:vboxmanage_not_found_error)
|
error_key(:vboxmanage_not_found_error)
|
||||||
end
|
end
|
||||||
|
|
|
@ -403,6 +403,9 @@ module VagrantPlugins
|
||||||
Vagrant::Util::Busy.busy(int_callback) do
|
Vagrant::Util::Busy.busy(int_callback) do
|
||||||
Vagrant::Util::Subprocess.execute(@vboxmanage_path, *command, &block)
|
Vagrant::Util::Subprocess.execute(@vboxmanage_path, *command, &block)
|
||||||
end
|
end
|
||||||
|
rescue Vagrant::Util::Subprocess::LaunchError => e
|
||||||
|
raise Vagrant::Errors::VBoxManageLaunchError,
|
||||||
|
message: e.to_s
|
||||||
end
|
end
|
||||||
end
|
end
|
||||||
end
|
end
|
||||||
|
|
|
@ -1231,6 +1231,13 @@ en:
|
||||||
Command: %{command}
|
Command: %{command}
|
||||||
|
|
||||||
Stderr: %{stderr}
|
Stderr: %{stderr}
|
||||||
|
vboxmanage_launch_error: |-
|
||||||
|
There was an error running VBoxManage. This is usually a permissions
|
||||||
|
problem or installation problem with VirtualBox itself, and not Vagrant.
|
||||||
|
Please note the error message below (if any), resolve the issue, and
|
||||||
|
try Vagrant again.
|
||||||
|
|
||||||
|
%{message}
|
||||||
vboxmanage_not_found_error: |-
|
vboxmanage_not_found_error: |-
|
||||||
The "VBoxManage" command or one of its dependencies could not
|
The "VBoxManage" command or one of its dependencies could not
|
||||||
be found. Please verify VirtualBox is properly installed. You can verify
|
be found. Please verify VirtualBox is properly installed. You can verify
|
||||||
|
|
Loading…
Reference in New Issue