Project

Profile

Help

Issue #2568

DocumentTooLarge error during merge of errata pkglists

Added by ttereshc over 4 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
2.12.1
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 15
Quarter:

Description

In certain cases new collections are added to the erratum pkglist with every sync, so at some point pkglist becomes so long that the BSON document size limit is reached.

Conditions to end up in this situation:

  • an erratum synced with Pulp < 2.8.5
  • upgrade to Pulp >= 2.8.5 (errata merge implemented)
  • pkglist for the same erratum changed upstream before the first operational sync (after Pulp upgrade) was performed
  • any operational sync at this point will add one more collection to erratum

It may sound like a rare case but according to BZ it is not, probably because pkglists were changed for errata in EPEL7 repo which a lot of users have in their Pulp.
For example, pkglist for erratum FEDORA-EPEL-2016-f057025262 was changed.


Related issues

Related to RPM Support - Issue #2599: Deprecation warning in the logs during errata migrationCLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>
Has duplicate RPM Support - Issue #2738: Errata package list exceed mongod 16MB document size limit.CLOSED - DUPLICATE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 03517e02 View on GitHub
Added by ttereshc over 4 years ago

Fix the errata merge logic

Pkglists should no longer be extended with the collections for the same repository. Migration is introduced to clean up duplicates in the affected pkglists.

closes #2568 https://pulp.plan.io/issues/2568

History

#1 Updated by ttereshc over 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc

#2 Updated by mhrivnak over 4 years ago

  • Severity changed from 2. Medium to 3. High
  • Triaged changed from No to Yes

#3 Updated by mhrivnak over 4 years ago

  • Sprint/Milestone set to 33

#4 Updated by ttereshc over 4 years ago

  • Status changed from ASSIGNED to POST

#5 Updated by ttereshc over 4 years ago

  • Status changed from POST to MODIFIED

#7 Updated by bizhang over 4 years ago

  • Platform Release set to 2.12.1

#8 Updated by bizhang over 4 years ago

  • Status changed from MODIFIED to 5

#9 Updated by bizhang over 4 years ago

  • Version set to 2.12.1

#10 Updated by demter@atix.de over 4 years ago

I have tested your changes against several katello instances running pulp-server-2.9.3-1.el7.noarch

they all seem to be running fine - syncing and content view publish works as expected again.

for the record - I simply used the changes in your pr. I ran pulp-manage-db --test
to not mess up the mongodb for future migrations and deleted the migration after I was done.

Thanks!

#11 Updated by bizhang over 4 years ago

  • Version deleted (2.12.1)

#12 Updated by ttereshc over 4 years ago

  • Related to Issue #2599: Deprecation warning in the logs during errata migration added

#13 Updated by bizhang over 4 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE

#15 Updated by ttereshc over 4 years ago

  • Has duplicate Issue #2738: Errata package list exceed mongod 16MB document size limit. added

#16 Updated by bmbouter over 3 years ago

  • Sprint set to Sprint 15

#17 Updated by bmbouter over 3 years ago

  • Sprint/Milestone deleted (33)

#18 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF