# \[Vote ended on 2026-09-24\] ACP 14.0.0: Possible violation of collection requirements from cisco.ucs **URL:** \ **Category:** Project Discussions\ **Tags:** collections, community-wg, collection-exclusion\ **Created:** [August 24, 2026, 5:47pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220 "2026-08-24T17:47:48Z")\ **Posts on this page:** 8\ **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:** [August 24, 2026, 5:47pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/1 "2026-08-24T17:47:48Z")
I’ve stumbled upon this collection when looking for [possibly unmaintained collections in ACP 14.0.0](https://forum.ansible.com/t/45864) because there hasn’t been a new release since [Apr 25, 2025](https://github.com/CiscoDevNet/ansible-ucs/releases/tag/v1.16.0). It looks like the last CI run has been on [Jun 27](https://github.com/CiscoDevNet/ansible-ucs/actions/runs/28281844306). So I think they violate our inclusion requirements. Additionally, I do not understand why their CI succeeded although all tests except those for the docs fragments look unhealthy. I’ve mentioned this in the [issue](https://github.com/CiscoDevNet/ansible-ucs/issues/57) I’ve opened in their repo. ---
**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:** [August 25, 2026, 4:09pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/2 "2026-08-25T16:09:18Z")
They’ve enabled the CI again. No new release for more than a year, though. This looks suspicious. On the other hand, maybe there really hasn’t been anything worth releasing 🤷 ---
**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:** [September 14, 2026, 6:43pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/3 "2026-09-14T18:43:26Z")
[This comment](https://github.com/CiscoDevNet/ansible-ucs/issues/57#issuecomment-5414351585) doesn’t sound really great: > No active development on this project for UCS Manager as development for UCS has moved to Intersight At least they say that: > We will still release here if there are any critical bug fixes. I don’t know what we should do about this 😧 ---
**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:** [September 14, 2026, 6:56pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/4 "2026-09-14T18:56:46Z")
This sounds pretty much like (not exactly though) a deprecated collection to me, so I think we should vote on removing it from a future Ansible 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:** [September 14, 2026, 7:11pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/5 "2026-09-14T19:11:41Z")
I don’t like the “not exactly” here. It would be easier if the collection would be officially deprecated. On the other hand, it looks like `cisco.intersight` is already part of the Ansible Community Package. This makes it somewhat easier. I’ll start a vote about removing `cisco.ucs` in some days if nobody objects. ---
**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:** [September 17, 2026, 4:55pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/6 "2026-09-17T16:55:19Z")
On the one hand, there’s no active development happening for this collection because it has been moved to Intersight (which is already [included in the community package](https://github.com/ansible-community/ansible-build-data/blob/a9dfbaaf2deb72ec3d839998d56006b8ce420138/14/ansible.in#L13)). On the other, they say they’ll still do releases for critical bugfixes. (see above) The problem here is that if there’s no active development happening on this collection, it’s always our problem to monitor that their CI is running, they’re testing with the latest ansible-core version (which is a requirement for being included in the Ansible Community Package) and so on. I think that the [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) has better things to do. So I’d like to start a vote on removing this collection, especially since it looks like there exists an alternative with `cisco.intersight`. _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/6))_ _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/6))_ edit: [Issue in their repo](https://github.com/CiscoDevNet/ansible-ucs/issues/58) ---
**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:** [September 22, 2026, 9:17am UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/7 "2026-09-22T09:17:47Z")
Seems like [Cisco UCS has moved to Intersight](https://github.com/CiscoDevNet/ansible-ucs/issues/57#issuecomment-5414351585): > No active development on this project for UCS Manager as development for UCS has moved to Intersight and the collection at [GitHub - CiscoDevNet/intersight-ansible: Cisco Intersight Ansible Collection · GitHub](https://github.com/CiscoDevNet/intersight-ansible). We will still release here if there are any critical bug fixes. ---
**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:** [September 24, 2026, 3:09pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-09-24-acp-14-0-0-possible-violation-of-collection-requirements-from-cisco-ucs/46220/8 "2026-09-24T15:09:28Z")
The vote ended today. 8 steering committee members voted in favor of removing `cisco.ucs` from Ansible 16 and no one against it, which means we’ve reached the quorum and the vote is accepted. There haven’t been any community votes.