search

ansible-community / ansible-build-data

Holds generated but persistent results from building the ansible community package
https://ansible.readthedocs.io/projects/ansible-build-data/
GNU General Public License v3.0
121 stars 43 forks source link

[Tracker] Serious collection requirements violations that require version pinning #223

Open gotmax23 opened 1 year ago

gotmax23 commented 1 year ago

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.

gotmax23 commented 1 year ago

cyberark.pas is again violating this guideline (https://github.com/ansible-community/ansible-build-data/pull/235#issuecomment-1556293107). I filed https://github.com/cyberark/ansible-security-automation-collection/issues/58.

felixfontein commented 1 year ago

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

felixfontein commented 1 year ago

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

felixfontein commented 1 year ago

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 commented 1 year ago

The issue with hetzner.hcloud is resolved (https://github.com/ansible-collections/hetzner.hcloud/issues/217, #267).

gotmax23 commented 1 year ago

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

https://github.com/ispim/inspur.ispim/issues/24

felixfontein commented 1 year ago
felixfontein commented 1 year ago

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 commented 1 year ago

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

felixfontein commented 1 year ago
felixfontein commented 1 year ago
gotmax23 commented 1 year ago
gotmax23 commented 1 year ago

https://github.com/Pure-Storage-Ansible/FlashArray-Collection/issues/500

sdodsley commented 1 year ago

Pure-Storage-Ansible/FlashArray-Collection#500

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

gotmax23 commented 11 months ago 
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 commented 11 months ago
felixfontein commented 11 months ago
felixfontein commented 9 months ago
felixfontein commented 7 months ago
felixfontein commented 7 months ago

community.ciscosmb introduced a breaking change in 1.0.8: https://github.com/ansible-collections/community.ciscosmb/issues/75

mariolenz commented 6 months ago

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 commented 6 months ago

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

felixfontein commented 5 months ago

cyberark.pas 1.0.27 is not tagged: https://github.com/cyberark/ansible-security-automation-collection/issues/71

felixfontein commented 4 months ago

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

felixfontein commented 1 month ago

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

felixfontein commented 1 month ago

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

mariolenz commented 1 week ago

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 commented 1 week ago

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