Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-16401

Satellite 6.12.2 - Big environment facing the deadlock after errata already applied - RHSA-2023:0261

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 6.13.z
    • 6.12.1
    • Pulp
    • 0
    • False
    • Moderate
    • None
    • None
    • None
    • None

      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:

              jira-bugzilla-migration RH Bugzilla Integration
              jira-bugzilla-migration RH Bugzilla Integration
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: