Race condition among capsule sync tasks to destroy/create pulp repos
|Assigned To:||Andrew Kofink|
|Category:||Foreman Proxy Content|
|Target version:||Team Brad - Iteration 12|
|Velocity based estimate||-|
|Release||Katello 3.3.2||Release relationship||Auto|
Description of problem:
Bulk capsule syncs failed when they were trying to remove the same pulp repos ('Actions::Katello::CapsuleContent::RemoveUnneededRepos').
Please see the below task information:
there are 7 Actions::Katello::CapsuleContent::Sync sub tasks in it matches the number of capsules in pnt-sysops org
each one of the capsulecontent::sync have one 'Actions::Katello::CapsuleContent::ConfigureCapsule'
and a lot of 'Actions::Pulp::Repository::Refresh'
under these 'Actions::Pulp::Repository::Refresh', some of them have skipped 'Actions::Pulp::Repository::RefreshDistributor'
under 'Actions::Katello::CapsuleContent::ConfigureCapsule', there is one 'Actions::Katello::CapsuleContent::RemoveUnneededRepos', where lots and lots of 'Actions::Pulp::Repository::Destroy' is in listed
'Actions::Pulp::Repository::Destroy' <-- lots of these are skipped or failed
The tasks paused after a whole bunch of repo::destroy failed. It can not be resumed until the user literally pressed the skip link next to every single errorred repo:destroy. The parent task can be resumed only when all of those errorred ones are skipped. After resuming, user got the Repo::create errors.