Actions
Issue #5569
closedCannot poll a collection import immediately after the collection is uploaded
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:
Quarter:
Description
The problem is that the task creates the CollectionImport object and so it cannot be polled until the task starts. This causes 404s for galaxy.
Updated by daviddavis about 5 years ago
- Status changed from NEW to POST
Updated by alikins about 5 years ago
@daviddavis @cutwater newswangerd I believe this may be same issue as https://gist.github.com/alikins/4cd34074fcfe294e9fa83933cd9e7279
Added by daviddavis about 5 years ago
Updated by daviddavis about 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp_ansible|c040a0bbdb2281e65b199c1013599037066767db.
Updated by alikins about 5 years ago
@daviddavis A similar issue:
https://github.com/ansible/galaxy-dev/issues/163
Most commentary is on pr at:
https://github.com/ansible/galaxy-api/pull/118
Updated by bmbouter about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Creating a CollectionImport immediately after the task
Galaxy was polling the CollectionImport which wasn't being created until the task started. This caused 404s.
fixes #5569