From 6dfc714c75b47314894e1e59c35c4c525914367c Mon Sep 17 00:00:00 2001
From: Ryan Petrello <rpetrell@redhat.com>
Date: Mon, 21 Oct 2019 11:01:35 -0400
Subject: [PATCH] when isolated or container jobs fail to launch, set job
 status to error

a status of error makes more sense, because failed generally points to
an issue with the playbook itself, while error is more generally used
for reporting issues internal to Tower

see: https://github.com/ansible/awx/issues/4909
---
 awx/main/isolated/manager.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/awx/main/isolated/manager.py b/awx/main/isolated/manager.py
index d78587cf7b..5a0555ed72 100644
--- a/awx/main/isolated/manager.py
+++ b/awx/main/isolated/manager.py
@@ -172,6 +172,7 @@ class IsolatedManager(object):
         if runner_obj.status == 'failed':
             self.instance.result_traceback = runner_obj.stdout.read()
             self.instance.save(update_fields=['result_traceback'])
+            return 'error', runner_obj.rc
 
         return runner_obj.status, runner_obj.rc