We have deployed the fix in cloud-2022-05-17. The missing collectionversions should now be sync'd.

Will be resolved by AAH-1540

Note, there is a workaround to sync the missing collectionversions: change the server url to https://console.redhat.com/api/automation-hub/content/published/ in order to sync down all certified collectionversions in the system, this url bypasses any synclist toggles the customer org admin has done.

While this issue is specifically about CollectionVersions, it is worth noting that the synclist has more collections than expected

• https://console.redhat.com/api/automation-hub/content/540155-synclist/v3/excludes/ shows the org admin has un-toggled 118 of the 120 collections
• https://console.redhat.com/api/automation-hub/content/540155-synclist/v3/collections/ shows the synclist has 87 collections when we expect 2 (120-118)

Adrian Likins it is true that the synclist repo is based on the latest upstream minus excludes. But the excludes are at the Collection level not the CollectionVersion level. So unless a synclist repo has excluded Collection A, it should have all CollectionVersions under Collection A that match what the upstream repo has.

Ah, indeed re CollectionVersions.

Though, and my memory is fuzzy, but at some point sync from a synclist repo  would only grab the latest of Collection A. That has likely changed (or I may be misremembering it anyway)

alikins@redhat.com it is true that the synclist repo is based on the latest upstream minus excludes. But the excludes are at the Collection level not the CollectionVersion level. So unless a synclist repo has excluded Collection A, it should have all CollectionVersions under Collection A that match what the upstream repo has.

Actual Behavior:

In my case, The latest version of azcollection is 1.09 and for my customer, it is 1.10. I think somehow sync list considers whatever version is available during its creation as latest version

AFAIK, that was the intended behavior. The syncable repo (synclist repo) will be based on the latest upstream plus any includes/excludes.

I confirmed that synclist repo https://console.redhat.com/ansible/automation-hub/repo/540155-synclist/azure/azcollection does not have all CollectionVersions that are in the published repo. This is mostly likely caused by a problem with our synclist curation AAH-1415, with some tasks failing early.

rhn-support-pghadge please try having a customer user who is an org-admin un-toggle and re-toggle the azcollection, the should update the synclist repo with all CollectionVersions. You can check this via this url and do not need to perform a sync: https://console.redhat.com/ansible/automation-hub/repo/540155-synclist/azure/azcollection