-
Bug
-
Resolution: Done
-
Major
-
None
-
Unspecified
-
None
-
False
-
-
False
-
-
-
Approved
Description
In the ansible-core CI, we have a process that creates and publishes many collections in parallel for later testing. This is largely to reduce the time of testing.
While updating the version of galaxy_ng that we test against, we have run into several concurrency issues with repo management in galaxy_ng.
Ultimately I believe they fall into 2 categories:
1. Race conditions removing versions that exceed retain_repo_versions
2. Race conditions creating new repo versions
Key Dependency Versions
galaxy-importer==0.4.10 galaxy-ng==4.7.0 pulp-ansible==0.17.0 pulp-container==2.14.5 pulp-glue==0.19.0 pulpcore==3.23.3
Steps to Reproduce
In short, create something like 50 collections, and publish them all in parallel to a single repository.
Actual Behavior
Various tracebacks. See attached files.
Expected Behavior
No tracebacks, all collections uploaded.
- is related to
-
AAH-2195 Testing performance and stage pipelines for system stability
- Closed
- mentioned on