Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.