Fix related to #13981

When working around "bad systems that insist on not allowing
updates in an atomic manner", we should not run previous exception
management code that tries to perform atomic move in case of
exception since the dirty non atomic move has already been
performed.

lib/ansible/module_utils/basic.py

@@ -1758,7 +1758,7 @@ class AnsibleModule(object):
                 # only try workarounds for errno 18 (cross device), 1 (not permitted),  13 (permission denied)
                 # and 26 (text file busy) which happens on vagrant synced folders and other 'exotic' non posix file systems
                 self.fail_json(msg='Could not replace file: %s to %s: %s' % (src, dest, e))
-
+            else:
                 dest_dir = os.path.dirname(dest)
                 dest_file = os.path.basename(dest)
                 try: