diff --git a/CHANGELOG.md b/CHANGELOG.md
index f17dd10e1..f22fd4fea 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,10 @@ BUG FIXES:
       galaxy resources when running on a Windows host [GH-6740, GH-6757]
   - provisioners/ansible_local: Change the way to verify `ansible-galaxy`
       presence, to avoid a non-zero status code with Ansible 2.0 [GH-6793]
+  - provisioners/ansible_local: The configuration sanity checks now only warn
+      on missing files or directories, so that the requested vagrant command is
+      always executed (e.g. `vagrant destroy` is not aborted when the configured
+      playbook is not present on the guest) [GH-6763]
 
 ## 1.8.1 (December 21, 2015)
 
diff --git a/plugins/provisioners/ansible/config/guest.rb b/plugins/provisioners/ansible/config/guest.rb
index 1845870ca..86ace3b58 100644
--- a/plugins/provisioners/ansible/config/guest.rb
+++ b/plugins/provisioners/ansible/config/guest.rb
@@ -41,12 +41,14 @@ module VagrantPlugins
 
           if machine.communicate.ready? && !machine.communicate.test("test #{test_args} #{remote_path}")
             if error_message_key
-              @errors << I18n.t(error_message_key, path: remote_path, system: "guest")
+              # only show warnings, as raising an error would abort the request
+              # vagrant action (e.g. prevent `destroy` to be executed)
+              machine.ui.warn(I18n.t(error_message_key, path: remote_path, system: "guest"))
             end
             return false
           end
           # when the machine is not ready for SSH communication,
-          # the check is "optimistically" by passed.
+          # the check is "optimistically" bypassed.
           true
         end