SCM job fails (usually can't reach github or such) but then all subsequent (non SCM) Jobs fail

Archives AWX Project
1

Problem…

  1. Occasionally, GitHub has problems and after some retries, can clear up and work for weeks fine.2. When the SCM job update failed in AWX all subsequent jobs start failing which then sets of a slew of alarms.
  2. Manually rerunning the SCM job and then the failed jobs usually unjams the Job queue.

Question…

Is it intended behaviour that when an SCM Job fails it blocks all future jobs?

BTW This did not happen in Ansible Tower 3.x over 2+ years. It seems ‘new behaviour’ in AWX 9.3.

Solution?
Is it possible to configure AWX to proceed with Job queue using a stale SCM working copy? (Assuming that the next SCM update job will succeed at some point and future Jobs will use a refreshed repo - which is fine for my purposes).

Thanks,
Mike.

2

Example SCM Error:

TASK [update project using git] ************************************************
17:01:39

6
fatal: [localhost]: FAILED! => {“changed”: false, “cmd”: “/usr/bin/git ls-remote origin -h refs/heads/master”, “msg”: “ERROR: \nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.”, “rc”: 128, “stderr”: “ERROR: \nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n”, “stderr_lines”: ["ERROR: ", “fatal: Could not read from remote repository.”, “”, “Please make sure you have the correct access rights”, “and the repository exists.”], “stdout”: “”, “stdout_lines”: }

Whatever the next set of incoming jobs are fail because of this SCM project-update failure before it.