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.

Description of problem:
The customer has 6.12.2 and after pushing some new lifecycle to diff capsules, they started facing the same deadlock issues that was already fixed via errata RHSA-2023:0261

Version-Release number of selected component (if applicable):
6.12.2

How reproducible:


Steps to Reproduce:
1. Create the lifecycle (multiple)
2. Create the cv/ccv/etc and promote them to the lifecycle

Actual results:
The customer faced deadlock as mentioned in article 
https://access.redhat.com/solutions/6718181

And it was on 4 capsules concurrently

Expected results:
Sync with no issues

Additional info:

I am happy to provide RCA in the linked case, or esp. identify if the deadlock there / reported by this BZ is the same like in https://bugzilla.redhat.com/show_bug.cgi?id=2170535 - but I havent found any SharedLock log or deadlock error in either sosreports of a Capsule - could you please navigate me to such sosreport / logs / capsule sync task?

Hello Pavel,

We requested already the complete tarball of "/var/log/*" of all affected Capsules servers. Once we receive it, we will share it here.

Thank you!
Waldirio

*** This bug has been marked as a duplicate of bug 2170535 ***