Previously, CV repos would be sync/published in any order. This could result in a situation where if your CV had a yum repo and a puppet repo, your puppet repo could get published first while the yum repo was still being synced. If the puppet repo had a module that referred to an RPM in the yum repo that was being published, this could result in puppet errors.
This commit re-orders CV publish so puppet repos are done last. Additionally, capsule syncs are broken apart so the non-puppet repos are synced in one concurrent block, and then once that's complete, puppet repos are synced in a second concurrent block.
Related issues
Bug #23672: CV publish can publish puppet before yum, causing provisioning issues
Added by Chris Duryee almost 6 years ago
Fixes #23672 - publish puppet repos last
Previously, CV repos would be sync/published in any order. This could
result in a situation where if your CV had a yum repo and a puppet
repo, your puppet repo could get published first while the yum repo
was still being synced. If the puppet repo had a module that referred
to an RPM in the yum repo that was being published, this could result
in puppet errors.
This commit re-orders CV publish so puppet repos are done last.
Additionally, capsule syncs are broken apart so the non-puppet repos
are synced in one concurrent block, and then once that's complete,
puppet repos are synced in a second concurrent block.