Actions
Issue #7512
closedSeeing 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.
Updated by alikins over 4 years ago
Example requirements.yml
collections:
- name: cisco.aci
- name: cisco.iosxr
- name: f5networks.f5_beacon
Updated by fao89 over 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
Added by Fabricio Aguiar over 4 years ago
Updated by pulpbot over 4 years ago
- Status changed from ASSIGNED to POST
Updated by Anonymous over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp_ansible|145011f7499b99cdfbb8bf7ac286c846942cfe3c.
Updated by pulpbot over 4 years ago
Updated by pulpbot about 4 years ago
Updated by pulpbot about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Fix skipped collections at requirements.yml
https://pulp.plan.io/issues/7512 closes #7512