[Vote ends on 2026-09-24] ACP 14.0.0: Possible violation of collection requirements from cisco.ucs

I’ve stumbled upon this collection when looking for possibly unmaintained collections in ACP 14.0.0 because there hasn’t been a new release since Apr 25, 2025.

It looks like the last CI run has been on Jun 27. 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 I’ve opened in their repo.

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 :person_shrugging:

This comment 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 :anguished_face:

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.

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.

1 Like

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). 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 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.

Steering Committee vote
  • Deprecate the collection and remove it from ACP 16
  • Keep the collection
0 voters
Community vote
  • Deprecate the collection and remove it from ACP 16
  • Keep the collection
0 voters

edit: Issue in their repo

1 Like