# \[Vote ended on 2026-02-19\] Possibly unmaintained collection: awx.awx **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg, awx, collections\ **Created:** [October 18, 2025, 1:45pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706 "2025-10-18T13:45:48Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 18, 2025, 1:45pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/1 "2025-10-18T13:45:48Z")
I’m not sure what we should do about this collection. On the one hand, it looks like there have been recent commits. On the other hand, there hasn’t been a new release since 2024. Additionally, there hasn’t been an answer to [Validate compatibility with ansible-core 2.19](https://github.com/ansible/awx/issues/15963). There are tests, but I don’t see sanity tests… especially not with ansible-core 2.19 or later. I tend to remove it from the Ansible Community Package. [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) What do you think? ---
**Author:** ![MalfuncEddie](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/malfunceddie/32/428_2.png) [@MalfuncEddie](https://forum.ansible.com/u/MalfuncEddie)\ **Post date:** [October 18, 2025, 4:26pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/2 "2025-10-18T16:26:03Z")
I’m sorry, there is major doubt/drama in the community about the state of the awx project during the rearcitecting and now it is suggested to remove the collection of awx what is a (hopefully) active project that will ever have another tagged release. **It’s collection in the ansible organisation!** I would freeze any discussion on this until the steering committee/redhat gives a clear message on the state of awx. I don’t believe Redhat would backtrack on the opensource commitment it gave, but discussions like this scare the living hell out of me. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 18, 2025, 5:02pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/3 "2025-10-18T17:02:18Z")
I moved the above two posts to a new topic since the discussion of whether the awx.awx collection should be part of the Ansible community distribution is somewhat unrelated and (as the second post shows) potentially very confusing in the context of the [orignal discussion](https://forum.ansible.com/t/streamlining-awx-releases/6894) (Edit: fixed link…). @MalfuncEddie collections included in the Ansible community distribution have to satisfy [certain rules](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html). Removal from the community distrubtion is totally unrelated to availability of the collection on Ansible Galaxy or Automation Hub, and what plans Red Hat has with AWX. Also the steering commitee has no say on AWX and anything AWX related, so the only ones who can say something on AWX are Red Hat. (Some individuals of the steering committee are RH employees and might or might not have more insight, or are part of the discussion; I’m only talking of the steering committee as a whole here.) The steering committee, on the other hand, is responsible for the Ansible community distribution. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 18, 2025, 5:20pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/4 "2025-10-18T17:20:10Z")
The collection tests are running ([Added Django and API requirements to AWX Contributor Docs for POC (#1… · ansible/awx@0d9483b · GitHub](https://github.com/ansible/awx/actions/runs/18568334414/job/52935441353)). The sanity tests seem to run with ansible-core 2.17, which is ancient, but the integration tests might (at least partially) run with the latest released ansible-core version (2.19.3) (I searched for `core 2.1` in the integration tests output). Considering our [guidelines on removal of unmaintained collections that have not been declared as deprecated](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#identifying-and-removing-an-unmaintained-collection-that-has-not-been-deprecated-by-its-maintainers), I’m not sure awx.awx fits this category - at least yet. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 18, 2025, 6:00pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/5 "2025-10-18T18:00:22Z")
Hi Thanks for splitting this into a separate discussion thread. I’m surprised that `ansible-test sanity` isn’t being run on the right versions of Ansible Core, thanks for raising that. These seem to be very specific things that Red Hat can fix, so let me let the AWX (Controller) team know these need fixing. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 19, 2025, 12:46pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/6 "2025-10-19T12:46:44Z")
> [@felixfontein](#): > > but the integration tests might (at least partially) run with the latest released ansible-core version (2.19.3) (I searched for `core 2.1` in the integration tests output) Good point! I didn’t spot this since the CI is a bit confusing to me. Anyway, they should also start to test with ansible-core 2.20 in order to be prepared for Ansible 13. For the record, I’m not _against_ keeping this collection in the Ansible Community Package. The current situation just looks a little bit unclear to me and I wanted to ask around. @MalfuncEddie As @felixfontein explained, this is not about killing the collection or something. It’s just about whether the collection still is compliant with the requirements to be kept in the [Ansible Community Package](https://pypi.org/project/ansible/). As I’ve said, the situation is a little bit unclear to me. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 20, 2025, 9:41am UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/7 "2025-10-20T09:41:46Z")
Currently the repo only tests against `stable-2.17`, I think that list needs updating to include 2.18. 2.19 & devel For reference, this is what is currently failing against devel: ```auto ERROR: Found 15 validate-modules issue(s) which need to be resolved: ERROR: plugins/inventory/controller.py:0:0: invalid-documentation: DOCUMENTATION.options.aap_token.env.0.deprecated.Any('alternatives', 'alternative', msg=None): required key not provided @ data['options']['aap_token']['env'][0]['deprecated'][Any('alternatives', 'alternative', msg=None)]. Got None ERROR: plugins/lookup/controller_api.py:0:0: invalid-documentation: DOCUMENTATION.options.aap_token.env.0.deprecated.Any('alternatives', 'alternative', msg=None): required key not provided @ data['options']['aap_token']['env'][0]['deprecated'][Any('alternatives', 'alternative', msg=None)]. Got None ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'credential_types' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'credentials' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'execution_environments' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'inventory' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'inventory_sources' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'job_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'notification_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'organizations' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'projects' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'schedules' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'teams' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'users' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'workflow_job_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec See documentation for help: https://docs.ansible.com/ansible-core/devel/dev_guide/testing/sanity/validate-modules.html ``` ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 20, 2025, 6:04pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/8 "2025-10-20T18:04:14Z")
The AWX (Controller) team will get this fixed. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [December 1, 2025, 5:27pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/9 "2025-12-01T17:27:34Z")
> [@felixfontein](#): > > Considering our [guidelines on removal of unmaintained collections that have not been declared as deprecated](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#identifying-and-removing-an-unmaintained-collection-that-has-not-been-deprecated-by-its-maintainers), I’m not sure awx.awx fits this category - at least yet. I think you’re right. There’s a lot of activity (although no new release yet) in the repo. So it doesn’t really qualify as being unmaintained. However, it looks like sanity tests are only run with ansible-core 2.17. This looks like a violation of our [CI testing requirements](https://docs.ansible.com/projects/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing): > You MUST run the `ansible-test sanity` command from the [latest stable ansible-base/ansible-core branch](https://github.com/ansible/ansible/branches/all?query=stable-). That’s different, but still not great. > [@gundalow](#): > > The AWX (Controller) team will get this fixed. Any news on this? After 6 weeks, I think it’s OK to ask. As I’ve said, as far as I can see there are still no sanity checks in the CI with ansible-core versions later than 2.17. I might be wrong there, though. I’ve just run a simple `grep -r '2\.1' .github/workflows/` and `grep -r '2\.2' .github/workflows/` and only found 2.17. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 10, 2026, 5:37pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/10 "2026-02-10T17:37:22Z")
Although there’s a lot of activity in the repo, there’s _still_ no new release. I’m not sure what we should do about this collection 😕 ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [February 10, 2026, 5:48pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/11 "2026-02-10T17:48:36Z")
I don’t know if this was mentioned, but the release versions of the awx.awx collection exactly match that of awx itself. So releases are only made when awx itself also sees a release. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 10, 2026, 6:05pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/12 "2026-02-10T18:05:59Z")
I don’t think that this has been mentioned yet, but I thought so. However, I don’t think that it really improves the situation that not only the collection but also AWX hasn’t seen a new release since 1 1/2 years. ---
**Author:** ![MalfuncEddie](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/malfunceddie/32/428_2.png) [@MalfuncEddie](https://forum.ansible.com/u/MalfuncEddie)\ **Post date:** [February 10, 2026, 6:59pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/13 "2026-02-10T18:59:05Z")
@mariolenz maybe this helps? > [@AWX modernization: Moving forward](https://forum.ansible.com/t/awx-modernization-moving-forward/45134): > > Hi folks, I’d like to give an update on the AWX modernization effort. Before we dive in, let’s briefly recap the [goals we defined](https://forum.ansible.com/t/refactoring-awx-into-a-pluggable-service-oriented-architecture/7404) for refactoring AWX into a pluggable, service-oriented architecture: Improved Flexibility: Easier to implement changes and add new features. Enhanced Maintainability: Simplified codebase with clear service boundaries. Better Code Reuse: More efficient reuse of code across different projects. Active Community Participation: Greater opportunity for community members … > Blockquote > In short, the AWX refactoring effort is nearing completion and there is no longer the need to use multiple branches for development. However there is still work to be done in our efforts to modernize the AWX codebase. ---
**Author:** ![thedoubl3j](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/thedoubl3j/32/103_2.png) [@thedoubl3j](https://forum.ansible.com/u/thedoubl3j)\ **Post date:** [February 10, 2026, 8:47pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/14 "2026-02-10T20:47:41Z")
Afternoon friends, as a maintainer of the awx collection, I can agree that it does not meet the standards set out for the community package. Whilst the collection is actively maintained and has changes merged into it/issues raised, we are not planning to cut a release because the modernization effort is ongoing. Given that we have not fully tested the collection against ansible-core stable 2.19, and do not align with the standards for the community package, I can see that removing the collection is the right action at this time. When the awx collection is ready to be included again, we will resubmit it and make sure it is updated and meets the standards of inclusion. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [February 10, 2026, 8:51pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/15 "2026-02-10T20:51:32Z")
@thedoubl3j Makes sense, +1 from me Thanks for the update ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 10, 2026, 9:01pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/16 "2026-02-10T21:01:33Z")
Out of curiosity, is there any estimate when a next release could happen? ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [February 11, 2026, 9:07am UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/17 "2026-02-11T09:07:53Z")
I don’t think that work is prioritized at the moment. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 11, 2026, 4:10pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/18 "2026-02-11T16:10:45Z")
Thanks for the clarification @thedoubl3j! [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) Maybe we really should remove the collection from Ansible 14. We can add it again later when the refactoring has been done and the collection is compatible with the ansible-core version ACP depends on. What do you think, should I start a vote? ---
**Author:** ![Akasurde](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akasurde/32/230_2.png) [@Akasurde](https://forum.ansible.com/u/Akasurde)\ **Post date:** [February 11, 2026, 4:35pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/19 "2026-02-11T16:35:04Z")
I agree, once the collection is ready, we can always submit the request for inclusion in ACP. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 11, 2026, 5:11pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/20 "2026-02-11T17:11:19Z")
👍 on voting. [Next page](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706.md?page=2)