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

Add a warning to a known capsule sync bug to upgrade to 6.12

XMLWordPrintable

    • Sat_docs_6_2024, Sat_docs_7_2024
    • No

      Document URL:

      https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/upgrading_and_updating_red_hat_satellite/index#performing-post-upgrade-tasks_upgrade-guide

      Section Number and Name:

      3.5. Performing Post-Upgrade Tasks

      Describe the issue:

      Upgrading Satellite to 6.12 includes rpm changelog being truncated to 10 entries for all pulp content. When Capsule is upgraded to 6.12 and a Capsule sync is invoked, https://bugzilla.redhat.com/show_bug.cgi?id=2170535 bug is highly probably hit as a direct consequence. Hitting the deadlock from the BZ (fixed in 6.13.z but not in 6.12) is a user experience we should warn about / prevent.

      Suggestions for improvement:

      Since there still can be customers upgrading to 6.12 and being supported on 6.12, we should warn about that deadlock bug. Please add a subsection like:

      "If you upgrade to 6.12 and plan running Capsule Sync here, be aware of https://bugzilla.redhat.com/show_bug.cgi?id=2170535 bug . Until you upgrade Capsule to 6.13, We recommend following KCS https://access.redhat.com/solutions/7002264 (in fact we recommend applying preventive workaround from https://access.redhat.com/solutions/6718181, that is `systemctl stop pulpcore-worker@

      {2..32}

      ` run on Capsule as a workaround)"

      Additional information:

              rhn-support-agadhave Akshay Gadhave
              jira-bugzilla-migration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: