Issue #7512
Seeing some collections skipped with CollectionRemote with requirements.yml (related to https://github.com/ansible/galaxy_ng/issues/437)
Description
This is kind of asking for a consult on https://github.com/ansible/galaxy_ng/issues/437
When testing standalone automation-hub that is setup for a remote that points to "community" (https://galaxy.ansible.com) when trying to sync with a remote that has a "requirements_file" specified, sometimes some collections are synced but others are ignored, seemingly with no errors.
The comments at https://github.com/ansible/galaxy_ng/issues/437 have more examples.
The current hypothesis is that it may just be malformed requirements.yml causing parts to be ignored.
But I'm looking for any other ideas that may need to be investigated.
Associated revisions
History
#1
Updated by alikins about 1 year ago
Example requirements.yml
collections:
- name: cisco.aci
- name: cisco.iosxr
- name: f5networks.f5_beacon
#2
Updated by fao89 about 1 year ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
#3
Updated by pulpbot about 1 year ago
- Status changed from ASSIGNED to POST
#4
Updated by Anonymous about 1 year ago
- Status changed from POST to MODIFIED
Applied in changeset pulp_ansible|145011f7499b99cdfbb8bf7ac286c846942cfe3c.
#5
Updated by pulpbot about 1 year ago
#6
Updated by daviddavis about 1 year ago
- Sprint/Milestone set to 0.4.0
#7
Updated by pulpbot about 1 year ago
#8
Updated by fao89 about 1 year ago
- Sprint set to Sprint 82
#9
Updated by pulpbot about 1 year ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Please register to edit this issue
.
Fix skipped collections at requirements.yml
https://pulp.plan.io/issues/7512 closes #7512