There are situations where users "Force Unlock" stuck tasks even after reading the warnings during different types of operations. This can lead to data integrity errors between Katello and Foreman. This results in having to execute similar 'repair' routines found here: https://access.redhat.com/solutions/1453313 Operations that are Force Unlocked that can cause issues include: * Repo Enable * Content View Publish * Content View Promote * Content View Deletion * Product Deletion * Organization Deletion We need to handle these situations in automated way with at least a daily check that will delete stale/miss-matched data and get the Satellite back into a working order.
Moving 6.2 bugs out to sat-backlog.
Various other fixes have gone into 6.2.z and 6.3 that minimize the need for a top level periodic check for mismatches like this. Going to close this out as no active work on this is taking place. Can re-open if we need to.