-
Bug
-
Resolution: Done
-
Undefined
-
None
-
2.3
-
None
-
False
-
-
False
-
-
Description
After editing the requirements.yml file for a different version range, PAH fails to sync the new content
Current workaround: Trigger the sync with optimize=false
curl https://huburl/api/galaxy/content/community/v3/sync/ -X POST -u admin:password -k--data-raw '{ optimize=false }'
Key Dependency Versions
{
"available_versions": {
"v3": "v3/",
"pulp-v3": "pulp/api/v3/"
},
"server_version": "4.6.4",
"galaxy_ng_version": "4.6.4",
"galaxy_ng_commit": "",
"galaxy_importer_version": "0.4.5",
"pulp_core_version": "3.21.3",
"pulp_ansible_version": "0.15.0",
"pulp_container_version": "2.14.1"
}
Steps to Reproduce
1) create requirements.yml
---
collections:
- name: community.general
version: ">=6.4.0"
2) configure PAH to sync with with file
3) validate the versions synced on the api
/api/galaxy/content/community/v3/plugin/ansible/content/community/collections/index/community/general/versions/
4) edit the requirements.yml with a new version range
---
collections:
- name: community.general
version: ">=6.0.0"
5) repeat steps 2 and 3
Actual Behavior
Only 3 collection versions are synced
{
"meta": {
"count": 3
},
Expected Behavior
8 collections
{
"meta": {
"count": 8
},
