Collection not compatible with ansible.utils 6.x.y

[gotmax23]

This collection is currently not compatible with ansible.utils 6.x.y per its galaxy.yml dependencies entry. Ansible 12 is expected to include ansible.utils v6, so please make sure to make your collection compatible as soon as possible.

According to the Ansible inclusion requirements (https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html#collection-dependencies), if you depend on any other collection, you have to make sure to be compatible to ansible.utils' latest version in a timely manner.

The requirements state:

In case a collection depends on releases of a new major version outside of this version range that will be included in the next major Ansible release, the dependent collection will be removed from the next major Ansible release. The cut-off date for this is feature freeze.

Please make sure to:

1. Update galaxy.yml's dependencies entry and make sure your collection is compatible to ansible.utils 6.x.y;
2. Release a new version with that change (note that dependency range updates should only be done in minor or major releases).

Note that Ansible 12 feature freeze takes place on June 17th, but please endeavor to make this update as soon as you can.

Thank you for your work and being part of the Ansible community package!

[felixfontein]

Ping @wastorga @racampos @jbogarin. Can you please fix this?

[felixfontein]

Also please note that this is the fourth time we had to remind you to update your ansible.utils dependency. Please either remove the upper cap, or set up some procedure that you are notified as soon as there is a new release of ansible.utils, so you can quickly update the upper cap without needing a reminder from our side. Thanks.

[jbogarin]

@felixfontein this collection is currently not being supported by our team. I already notified the Cisco team about it.

[felixfontein]

@jbogarin any news?

Also CC @bvargasre who merged something some months ago.

[jbogarin]

He is also part of my team. I already sent this information to the Cisco team and a follow up email, it's on their side.

[felixfontein]

Any update on this?

[s-hertel]

I was curious what the collection depended on ansible.utils for, and it's only for action plugin argument spec validation. This can be done easily with ansible-core, so I automated a fix for what it's worth: #161

[felixfontein]

FYI, we've removed the collection from Ansible 12 for now; if the issues are fixed and the collection is sufficiently tested with ansible-core 2.19 before the feature freeze we can re-add it to Ansible 12, but if there are no indications that something is happening, it will stay out of Ansible 12.

Ref: https://forum.ansible.com/t/43367

[fmunozmiranda]

Solved