You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that AWX is open source software provided for free and that I might not receive a timely response.
Bug Summary
The propagation of the cancellation signals is not working 100% as intended.
If you launch a job on a cluster that needs to run a project sync in advance to sync the source tree, and you cancel the job in the right time window, the project update will give an error status with the message:
Task was canceled due to receiving a shutdown signal.
We don't want this, we want a plain "canceled" status instead (or in the absence of that, an appropriate message).
AWX version
devel
Select the relevant components
UI
API
Docs
Collection
CLI
Other
Installation method
docker development environment
Modifications
no
Ansible version
N/A
Operating system
N/A
Web browser
Chrome
Steps to reproduce
Launch a job on a cluster, so that it's likely that it will trigger a project sync before-hand to update the source tree on the node it runs on.
Quickly cancel the job.
Expected results
Job will get canceled status.
Actual results
Job gets this status
This is because the project update error followed through the fail chain. Click on the project link in that page:
So that's the bug there.
Additional information
This was triggered indirectly via a workflow as well.
Please confirm the following
Bug Summary
The propagation of the cancellation signals is not working 100% as intended.
If you launch a job on a cluster that needs to run a project sync in advance to sync the source tree, and you cancel the job in the right time window, the project update will give an error status with the message:
We don't want this, we want a plain "canceled" status instead (or in the absence of that, an appropriate message).
AWX version
devel
Select the relevant components
Installation method
docker development environment
Modifications
no
Ansible version
N/A
Operating system
N/A
Web browser
Chrome
Steps to reproduce
Launch a job on a cluster, so that it's likely that it will trigger a project sync before-hand to update the source tree on the node it runs on.
Quickly cancel the job.
Expected results
Job will get canceled status.
Actual results
Job gets this status
This is because the project update error followed through the fail chain. Click on the project link in that page:
So that's the bug there.
Additional information
This was triggered indirectly via a workflow as well.
Is the data determined from the scenario given above. The bug is that the project update should probably have had the cancel_flag flipped.
this is probably fallout from #12435
The text was updated successfully, but these errors were encountered: