provisioners/ansible_local: fix a lame bug
I missed to rename the refactored exceptions as AnsibleCommandFailed in
the guest-based parts. The lack of unit tests for these parts hurts...
on my agenda, I swear!
See c1f3d114f5
This commit is contained in:
parent
5659c3f2a0
commit
74eb3109cf
|
@ -74,7 +74,7 @@ module VagrantPlugins
|
||||||
ui_running_ansible_command "galaxy", remote_command
|
ui_running_ansible_command "galaxy", remote_command
|
||||||
|
|
||||||
result = execute_on_guest(remote_command)
|
result = execute_on_guest(remote_command)
|
||||||
raise Ansible::Errors::AnsibleGalaxyAppFailed if result != 0
|
raise Ansible::Errors::AnsibleCommandFailed if result != 0
|
||||||
end
|
end
|
||||||
|
|
||||||
def execute_ansible_playbook_on_guest
|
def execute_ansible_playbook_on_guest
|
||||||
|
@ -87,7 +87,7 @@ module VagrantPlugins
|
||||||
ui_running_ansible_command "playbook", remote_command
|
ui_running_ansible_command "playbook", remote_command
|
||||||
|
|
||||||
result = execute_on_guest(remote_command)
|
result = execute_on_guest(remote_command)
|
||||||
raise Ansible::Errors::AnsiblePlaybookAppFailed if result != 0
|
raise Ansible::Errors::AnsibleCommandFailed if result != 0
|
||||||
end
|
end
|
||||||
|
|
||||||
def execute_on_guest(command)
|
def execute_on_guest(command)
|
||||||
|
|
Loading…
Reference in New Issue