Orphan cleanup task does not consider that some package lists associated with an errata are no longer needed because the repository associated with them is no longer present. This can cause the errata to grow so large that it is too big to store in MongoDB. As a result a user will experience BZ #1410649.
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
I changed summary just to better reflect the issue, nothing new. Description: This error can occur during sync or errata upload and it is more likely to happen in the following situations: - many repositories of the same content were created, removed, created again.(package list grows, orphan clean up does not touch package lists). - too many individual repositories (which have feed and were not created via copy). Both (especially last one) are the cases for a Capsule sync, so most likely this error will be seen on a Capsule and not on a main Satellite.
*** Bug 1450513 has been marked as a duplicate of this bug. ***
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Verified in Satellite 6.2.11 Snap 2. The automated test for this bug has been passing since snap 1. Test automated in https://github.com/SatelliteQE/robottelo/pull/4766
*** Bug 1474382 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2466