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

Deadlock seen when publishing a content view

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Content Views
    • 0
    • False
    • Important
    • None
    • None
    • None
    • None
    • No

      Description of problem:
      When publishing a content view, encountering a deadlock

      Version-Release number of selected component (if applicable):
      python39-pulpcore-3.21.18-1.el8pc.noarch
      satellite-6.13.5-1.el8sat.noarch

      How reproducible:
      Not reproducible

      Steps to Reproduce:
      1.
      2.
      3.

      Actual results:
      ""class"":""Dynflow::ExecutionPlan::Steps::Error"",""exception_class"":""ActiveRecord::Deadlocked"",""message"":""PG::TRDeadlockDetected: ERROR: deadlock detected\nDETAIL: Process 3250880 waits for ShareLock on transaction 62043418; blocked by process 3271050.\nProcess 3271050 waits for ShareLock on transaction 62043419; blocked by process 3250880.\nHINT: See server log for query details.\nCONTEXT: while inserting index tuple (472,1) in relation \""katello_errata\""\n""}",,

      Expected results:
      No deadlock

      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:
              1 Start watching this issue

                Created:
                Updated: