[Tracker] Serious collection requirements violations that require version pinning

[gotmax23]

As per https://github.com/ansible-community/ansible-build-data/blob/main/docs/policies.md#enforcement, we need to track violations of the Repository management policies. We also need to track violations when collection dependencies conflicts arise, or collections violate semantic versioning by doing breaking changes outside of major versions. When you file an issue against a collection for violating these policies, leave a comment with a link to the issue.

• Collection Requirements Violation - Repository Management (2) cyberark/ansible-security-automation-collection#58
• Ansible 8 depclosure error in dellemc.enterprise_sonic #233
• Collection Requirements Violation - Semantic Versioning ansible-collections/dellemc.enterprise_sonic#268
• Collection Requirements Violation - Semantic Versioning ansible-collections/hetzner.hcloud#217
• inspur.ispim 2.0.1 is not tagged in https://github.com/ispim/inspur.ispim ispim/inspur.ispim#24
• cisco.intersight 2.0.2 is not tagged in https://github.com/CiscoDevNet/intersight-ansible CiscoDevNet/intersight-ansible#93
• netapp.aws 21.7.1 is not tagged ansible-collections/netapp.aws#8
• netapp.azure 21.10.1 is not tagged ansible-collections/netapp.azure#8
• netapp.cloudmanager 21.22.1 is not tagged ansible-collections/netapp.cloudmanager#9
• netapp.um_info 21.8.1 is not tagged ansible-collections/netapp.um_info#10
• fortinet.fortios 2.3.4 is not tagged fortinet-ansible-dev/ansible-galaxy-fortios-collection#277
• semver violation: purestorage.flasharray 1.22.0 contains Breaking Changes Pure-Storage-Ansible/FlashArray-Collection#500
• Please add support ansible.utils v3 meraki/dashboard-api-ansible#38
• Please add support for ansible.utils v3 cisco-en-programmability/dnacenter-ansible#133
• Please add support ansible.utils v3 CiscoISE/ansible-ise#112
• cisco.dnac 6.10.0 is not tagged cisco-en-programmability/dnacenter-ansible#142
• ibm.storage_virtualize 2.2.0 is not tagged ansible-collections/ibm.storage_virtualize#36
• infinidat.infinibox 1.4.0 is not tagged Infinidat/ansible-infinidat-collection#20
• Collection must be made compatible with newly released ansible.utils 4.0.0 ASAP cisco-en-programmability/dnacenter-ansible#160
• Collection must be made compatible with newly released ansible.utils 4.0.0 ASAP meraki/dashboard-api-ansible#49
• Collection must be made compatible with newly released ansible.utils 4.0.0 ASAP CiscoISE/ansible-ise#123
• Collection Requirements Violation - Semantic Versioning ansible-collections/community.ciscosmb#75
• Collection Requirements Violation - Semantic Versioning ansible-collections/community.grafana#367
• cyberark.pas 1.0.27 is not tagged cyberark/ansible-security-automation-collection#71
• Violation of semantic versioning ansible-collections/ansible.posix#463
• Collection not compatible with ansible.utils 5.x.y cisco-en-programmability/dnacenter-ansible#192
• Collection not compatible with ansible.utils 5.x.y meraki/dashboard-api-ansible#67
• Collection not compatible with ansible.utils 5.x.y CiscoISE/ansible-ise#144

[gotmax23]

cyberark.pas is again violating this guideline (#235 (comment)). I filed cyberark/ansible-security-automation-collection#58.

[felixfontein]

dellemc.enterprise_sonic needs to be pinned to 2.0.0 in both Ansible 7 and Ansible 8 for two violations:

• (applies only to Ansible 8) [Tracker] Serious collection requirements violations that require version pinning #223 / [BUG]: Collection does not support ansible.netcommon 5.x.y, thus latest version will not be included in Ansible 8 until this is fixed ansible-collections/dellemc.enterprise_sonic#267
• (applies to both Ansible 7 and 8) Collection Requirements Violation - Semantic Versioning ansible-collections/dellemc.enterprise_sonic#268

[felixfontein]

hetzner.hcloud needs to be pinned to 1.11.0 in both Ansible 7 and 8 for a semantic versioning violation: ansible-collections/hetzner.hcloud#217

[felixfontein]

There has been a new release of dellemc.enterprise_sonic (2.2.0) which reverts the breaking change and declares compatibility with ansible.netcommon >5.0.0. This fixes the problems with Ansible 8 (except that the breaking change will still be mentioned in the next porting guide, even though it is no longer a breaking change - I guess we have to add an Ansible changelog entry for that), but has the downside of not allowing this release for the next Ansible 7 release since that one has ansible.netcommon 4.x.y. So we have to keep the pin for Ansible 7 (though now it has another reason), and undo it (with a changelog entry) for Ansible 8.

[felixfontein]

The issue with hetzner.hcloud is resolved (ansible-collections/hetzner.hcloud#217, #267).

[gotmax23]

inspur.ispim 2.0.1 is not tagged in https://github.com/ispim/inspur.ispim

ispim/inspur.ispim#24

[felixfontein]

• cisco.intersight 2.0.2 is not tagged in https://github.com/CiscoDevNet/intersight-ansible (cisco.intersight 2.0.2 is not tagged in https://github.com/CiscoDevNet/intersight-ansible CiscoDevNet/intersight-ansible#93, Ansible 9 CI: ignore missing tag for cisco.intersight for now #287)
• cisco.meraki 2.16.0 is not tagged in https://github.com/CiscoDevNet/ansible-meraki

[felixfontein]

cisco.meraki moved to a new repository: https://github.com/meraki/dashboard-api-ansible - I'll create PRs for ansible-build-data to adjust it.

[felixfontein]

cisco.intersight was now tagged, #289 removed the ignore for the missing tags.

[felixfontein]

• netapp.aws 21.7.1 is not tagged in https://github.com/ansible-collections/netapp.aws: netapp.aws 21.7.1 is not tagged ansible-collections/netapp.aws#8
• netapp.azure 21.10.1 is not tagged in https://github.com/ansible-collections/netapp.azure: netapp.azure 21.10.1 is not tagged ansible-collections/netapp.azure#8
• netapp.cloudmanager 21.22.1 is not tagged in https://github.com/ansible-collections/netapp.cloudmanager: netapp.cloudmanager 21.22.1 is not tagged ansible-collections/netapp.cloudmanager#9
• netapp.um_info 21.8.1 is not tagged in https://github.com/ansible-collections/netapp.um_info: netapp.um_info 21.8.1 is not tagged ansible-collections/netapp.um_info#10

[felixfontein]

• fortinet.fortios 2.3.4 is not tagged in https://github.com/fortinet-ansible-dev/ansible-galaxy-fortios-collection: fortinet.fortios 2.3.4 is not tagged fortinet-ansible-dev/ansible-galaxy-fortios-collection#277

[gotmax23]

• purestorage.flasharray 1.22.0 contains Breaking Changes

[gotmax23]

Pure-Storage-Ansible/FlashArray-Collection#500

[sdodsley]

Pure-Storage-Ansible/FlashArray-Collection#500

Resolved - poor usage of flag in the changelog. Changelogs fixed and new Collection version released

[gotmax23]

ERROR: found collection dependency errors!
ERROR: cisco.ise 2.6.2 version_conflict: ansible.utils-3.0.0 but needs >=2.0.0,<3.0
ERROR: cisco.dnac 6.8.1 version_conflict: ansible.utils-3.0.0 but needs >=2.0.0,<3.0
ERROR: cisco.meraki 2.16.16 version_conflict: ansible.utils-3.0.0 but needs >=2.0.0,<3.0

[gotmax23]

• cisco.meraki: Please add support ansible.utils v3 meraki/dashboard-api-ansible#38
• cisco.dnac: Please add support for ansible.utils v3 cisco-en-programmability/dnacenter-ansible#133
• cisco.ise: Please add support ansible.utils v3 CiscoISE/ansible-ise#112

[felixfontein]

• cisco.dnac 6.10.0 is not tagged: cisco.dnac 6.10.0 is not tagged cisco-en-programmability/dnacenter-ansible#142
• ibm.storage_virtualize 2.2.0 is not tagged: ibm.storage_virtualize 2.2.0 is not tagged ansible-collections/ibm.storage_virtualize#36

[felixfontein]

• infinidat.infinibox 1.4.0 is not tagged: infinidat.infinibox 1.4.0 is not tagged Infinidat/ansible-infinidat-collection#20

[felixfontein]

• ERROR: cisco.dnac 6.13.1 version_conflict: ansible.utils-4.0.0 but needs >=2.0.0,<4.0: Collection must be made compatible with newly released ansible.utils 4.0.0 ASAP cisco-en-programmability/dnacenter-ansible#160
• ERROR: cisco.meraki 2.17.2 version_conflict: ansible.utils-4.0.0 but needs >=2.0.0,<4.0: Collection must be made compatible with newly released ansible.utils 4.0.0 ASAP meraki/dashboard-api-ansible#49
• ERROR: cisco.ise 2.8.0 version_conflict: ansible.utils-4.0.0 but needs >=2.0.0,<4.0: Collection must be made compatible with newly released ansible.utils 4.0.0 ASAP CiscoISE/ansible-ise#123

[felixfontein]

community.ciscosmb introduced a breaking change in 1.0.8: ansible-collections/community.ciscosmb#75

[mariolenz]

It looks like frr.frr fails a lot of tests. I don't care about the unit tests but the failing sanity tests are problematic. I've opened ansible-collections/frr.frr#66 to let them know.

[mariolenz]

community.grafana introduced a breaking change (removed feature) in 1.9.0: ansible-collections/community.grafana#367

[felixfontein]

cyberark.pas 1.0.27 is not tagged: cyberark/ansible-security-automation-collection#71

[felixfontein]

It's too late for version pinning since 2.6.0 of that collection has been included for some months now, but FYI: CiscoDevNet/ansible-mso#479 - I've created https://forum.ansible.com/t/7039 for this.

[felixfontein]

ansible.posix 1.6.0 has a breaking change (ansible-collections/ansible.posix#463 (comment)). #469 restricts it to < 1.6.0 for Ansible 9 and 10. For Ansible 11, we have to see what happens.

[felixfontein]

cisco.dnac, cisco.meraki, and cisco.ise still require ansible.utils < 5.0.0 (pinned in #480 for Ansible 11).

[mariolenz]

cisco.dnac 6.24.0 isn't tagged: cisco-en-programmability/dnacenter-ansible#205

I suggest to wait a few days until we introduce a restriction. Maybe they'll fix this soon.

[felixfontein]

The problem has been resolved, the release is now tagged.