Alan RomingerandClaude Opus 4.6
3ab18fd58f
The EE sidecar container creates /etc/receptor/receptor.conf on pod startup. If the task container's dispatcherd reaches the heartbeat before the config exists, the instance rejoins the cluster at full capacity with no receptor — causing fatal job failures with no recovery path. Three layers of defense: 1. dispatcherd management command: poll for the receptor config file before entering the main loop (10s timeout, exits with error to let k8s restart the container). 2. Heartbeat: if get_receptor_ctl() raises FileNotFoundError (config or socket missing), mark the instance offline so no jobs are dispatched to it. Previously this was silently ignored and the instance kept full capacity. 3. should_update_config(): catch FileNotFoundError and return True so write_receptor_config() can create the file on first boot instead of crashing. Prior art: #12698 (closed without merge) took a broader approach with custom exception types. See PR comment for overlap analysis. Closes: AAP-89010 Co-authored-by: Claude Opus 4.6 <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.