Project

Profile

Help

Issue #7512

closed

Seeing some collections skipped with CollectionRemote with requirements.yml (related to https://github.com/ansible/galaxy_ng/issues/437)

Added by alikins about 2 years ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
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.

Actions #1

Updated by alikins about 2 years ago

Example requirements.yml

collections:
  - name: cisco.aci
  - name: cisco.iosxr
  - name: f5networks.f5_beacon
Actions #2

Updated by fao89 about 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89

Added by Fabricio Aguiar about 2 years ago

Revision 145011f7

Fix skipped collections at requirements.yml

https://pulp.plan.io/issues/7512 closes #7512

Actions #3

Updated by pulpbot about 2 years ago

  • Status changed from ASSIGNED to POST
Actions #4

Updated by Anonymous about 2 years ago

  • Status changed from POST to MODIFIED
Actions #6

Updated by daviddavis about 2 years ago

  • Sprint/Milestone set to 0.4.0
Actions #8

Updated by fao89 about 2 years ago

  • Sprint set to Sprint 82
Actions #9

Updated by pulpbot about 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF