# Cisco.ucs 1.16.0 violates ACP requirements

**URL:** <https://forum.ansible.com/t/cisco-ucs-1-16-0-violates-acp-requirements/45737>\
**Category:** Project Discussions\
**Tags:** cisco, community-wg, collections\
**Created:** [April 25, 2026, 12:57pm UTC](https://forum.ansible.com/t/cisco-ucs-1-16-0-violates-acp-requirements/45737 "2026-04-25T12:57:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**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:** [April 25, 2026, 12:57pm UTC](https://forum.ansible.com/t/cisco-ucs-1-16-0-violates-acp-requirements/45737/1 "2026-04-25T12:57:56Z")

</div>

I think that `cisco.ucs` violates our requirements for [CI Testing](https://docs.ansible.com/projects/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing):

1. As far as I can see, sanity tests don’t include ansible-core 2.20 [currently](https://github.com/CiscoDevNet/ansible-ucs/blob/c95cefe33999d09f367deec62eda3f954011a2a3/.github/workflows/main.yml#L62-L81). (Actually, I think they should have added even 2.21 [by now](https://forum.ansible.com/t/45646).)
2. And, anyway, the last CI run seems to have been [Jun 30, 2025](https://github.com/CiscoDevNet/ansible-ucs/actions/runs/15965209810).

What should we do about this?

---

<div class="post-metadata">

**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:** [April 25, 2026, 2:05pm UTC](https://forum.ansible.com/t/cisco-ucs-1-16-0-violates-acp-requirements/45737/2 "2026-04-25T14:05:26Z")

</div>

I guess the best would be to create an issue in the collection’s repo and see whether there’s a reply.

Maybe we should start a tracker similar to the one in [[Tracker] Serious collection requirements violations that require version pinning · Issue #223 · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/issues/223) that’s for “other” violations that do not block inclusion in a release. Anyone has a good idea where such a tracker should stay? The issue is OK for tracking things that don’t happen too often, but general violations might be more common. Maybe we should use an issue board where we can attach issues from various repos? (Does that actually trigger notifications, i.e. when an issue is added, moved to another column, …?)

---

<div class="post-metadata">

**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:** [April 26, 2026, 1:51pm UTC](https://forum.ansible.com/t/cisco-ucs-1-16-0-violates-acp-requirements/45737/3 "2026-04-26T13:51:14Z")

</div>

I’ve created an issue: [CI doesn’t satisfy ACP requirements](https://github.com/CiscoDevNet/ansible-ucs/issues/55)

---

<div class="post-metadata">

**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:** [April 27, 2026, 4:31pm UTC](https://forum.ansible.com/t/cisco-ucs-1-16-0-violates-acp-requirements/45737/4 "2026-04-27T16:31:47Z")

</div>

They’ve added 2.20 and 2.21 and there has been a [CI run today](https://github.com/CiscoDevNet/ansible-ucs/actions/runs/25002890839).

I think it’s somewhat weird that there hasn’t been a new release since a year, but that’s a different discussion.