2and3makes23
2and3makes23
@fosterseth > @fust @2and3makes23 do you get the 502 if you append ?x= when landing on the job output page > e.g. #/jobs/playbook/10/output?x= We will try that as soon as...
@fosterseth We have two Error-state jobs again (IDs: 161866, 161867), they derive from the same job template. Like you I tried querying `.../api/v2/jobs/161867/job_events/children_summary` (same behavior for both jobs this morning):...
We have the same issue at our firm, so I'll second this feature request.
> > are the state of these running Job still managed by the remaining AWX pods? The [README](https://github.com/ansible/awx-operator/#pods-termination-grace-period) states: ``` During deployment restarts or new rollouts, when old ReplicaSet Pods...
## Fire-and-forget deployment Currently the AWX Operator checks for present deployments [[1](https://github.com/ansible/awx-operator/blob/07427be0b79411f5c8fd2ffd7caf4fd92fcce47a/roles/installer/tasks/main.yml#L35)] and removes respective resources before redeployment [[2](https://github.com/ansible/awx-operator/blob/07427be0b79411f5c8fd2ffd7caf4fd92fcce47a/roles/installer/tasks/install.yml#L2)]. If I understand this correctly, it´s like a fire-and-forget approach to...
We are experiencing long (several minutes) waiting times during which inventories we delete stay in "pending delete" state. At least since one of the last updates (I believe 21.7), inventory...
What we ended up doing is always deleting the inventory´s hosts first, which seemed to resolve the issue of pending deletion inventories. Empty inventories always get deleted instantly. Maybe this...
Hi there, we see this (or a very similar looking) stack trace regularly as well. Is it possible to add a check for existence [somewhere here](https://github.com/ansible/awx/blob/devel/awx/main/tasks/system.py#L373-379) to prevent this from...
We would love this feature as well. Some of our teams have large repositories where `.git/` uses several hundreds MB of disk space. 🙈 This delays job starts. When cloning...
Would it be possible to allow graph cycles with approval nodes to achieve something similar to "resume after failure"? This would enable placing an approval node behind critical actions that...