Issue #7512
Seeing some collections skipped with CollectionRemote with requirements.yml (related to https://github.com/ansible/galaxy_ng/issues/437)
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 82
Quarter:
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
#4
Updated by Anonymous 4 months ago
- Status changed from POST to MODIFIED
Applied in changeset pulp_ansible|145011f7499b99cdfbb8bf7ac286c846942cfe3c.
#6
Updated by daviddavis 4 months ago
- Sprint/Milestone set to 0.4.0
Please register to edit this issue
Fix skipped collections at requirements.yml
https://pulp.plan.io/issues/7512 closes #7512