Chris MeyersandClaude
274d5abed8
Adopting an orphaned job now claims it first: the heartbeat replaces the job's celery_task_id with a new task id, only if it still holds the value the heartbeat read, and then dispatches adopt_job_async under that id. Previously the task was dispatched first and its id recorded after, and two heartbeats could both record one. Final status writes are fenced by that id. update_model takes owner_task_id and raises NotOwner, writing nothing, when the job's celery_task_id no longer matches. BaseTask.run passes the id it was dispatched under, and adoption passes its claimed id. A task that loses ownership neither writes its final status nor releases the work unit, which now belongs to the new owner. An adoption whose claim was replaced before it starts does nothing. Cancels follow celery_task_id, so they go to the current owner. This changes behavior: a controller that only looked dead can no longer overwrite an adopted job's result when it comes back. Co-Authored-By: Claude <noreply@anthropic.com>
Caution
The last release of this repository was released on Jul 2, 2024. Releases of this project are now paused during a large scale refactoring. For more information, follow the Forum and - more specifically - see the various communications on the matter:
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
To install AWX, please view the Install guide.
To learn more about using AWX, view the AWX docs site.
The AWX Project Frequently Asked Questions can be found here.
The AWX logos and branding assets are covered by our trademark guidelines.
Contributing
- Refer to the Contributing guide to get started developing, testing, and building AWX.
- All code submissions are made through pull requests against the
develbranch. - All contributors must use
git commit --signofffor any commit to be merged and agree that usage of--signoffconstitutes agreement with the terms of DCO 1.1 - Take care to make sure no merge commits are in the submission, and use
git rebasevs.git mergefor this reason. - If submitting a large code change, it's a good idea to join discuss via the Ansible Forum. This helps everyone know what's going on, and it also helps save time and effort if the community decides some changes are needed.
Reporting Issues
If you're experiencing a problem that you feel is a bug in AWX or have ideas for improving AWX, we encourage you to open an issue and share your feedback. But before opening a new issue, we ask that you please take a look at our Issues guide.
Code of Conduct
We require all of our community members and contributors to adhere to the Ansible code of conduct. If you have questions or need assistance, please reach out to our community team at codeofconduct@ansible.com
Get Involved
We welcome your feedback and ideas via the Ansible Forum.
For a full list of all the ways to talk with the Ansible Community, see the AWX Communication guide.