Open gotmax23 opened 9 months ago
I think you can ignore some of those collections since they'll be removed from Ansible 10 anyway:
BTW I see purestorage.fusion on your list. It looks like this collection will be deprecated. So maybe you can ignore this, too.
BTW I see purestorage.fusion on your list. It looks like this collection will be deprecated. So maybe you can ignore this, too.
@gotmax23 This collection has been deprecated by it's maintainers and will be removed from Ansible 10: ansible-community/ansible-build-data#374
Results for 10.3.0 are listed below and also represented in https://github.com/ansible-community/package-test-results/tree/main/rendered/10.3.0. Some of the duplicates from above may have been fixed in git but never released. Other have not fixed all the issues or not responded at all.
(Duplicates that are already listed in the issue description and that have had issues filled already should be checked off here.)
Followed up with:
(Will follow up again in a couple weeks)
@gundalow followed up with
(We should follow up again in a couple weeks)
are also a problem. The maintainer says that our results are broken and differ from the results reported by Automation Hub. Perhaps there are sanity ignore entries that are not included in the git repository. Otherwise, I am at a loss.
@gundalow, any idea what's going on with the Cisco collections? Looking at the output in https://console.redhat.com/ansible/automation-hub/repo/published/cisco/intersight/import-log/, it seems that AH doesn't run the validate-modules test which is one that we require to pass.
A discussion about community.network has been started in https://forum.ansible.com/t/should-we-remove-community-network-from-the-ansible-community-package/8030.
[ ] Community package requirements: sanity tests CiscoDevNet/ansible-ucs#40 (current results at https://github.com/ansible-community/package-test-results/blob/main/rendered/10.3.0/cisco.ucs.md)
are also a problem. The maintainer says that our results are broken and differ from the results reported by Automation Hub. Perhaps there are sanity ignore entries that are not included in the git repository. Otherwise, I am at a loss.
It turned out that this is actually due to a bug in ansible-test (https://github.com/ansible/ansible/issues/83842). On the other hand, if Automation Hub's sanity tests accepted it, it means that AH doesn't run the validate-modules sanity test. This basically means that successful import in AH doesn't mean that all sanity tests pass. (But it also doesn't mean that the ones not run fail...)
(All the collections that have been retired from Ansible 10.3.0 or otherwise no longer have sanity test failures in that version should be checked off.)