The Pulp 2 to Pulp 3 migration stucks and raises 'pymongo.errors.DocumentTooLarge' error in /var/log/messages file

Environment

• Red Hat Satellite 6.9

Issue

• The Pulp 2 to Pulp 3 migration stucks and raises the following pymongo.errors.DocumentTooLarge error in /var/log/messages file:

  pulpcore-worker-4: RuntimeWarning)
  pulpcore-worker-4: pulp: rq.worker:ERROR: Traceback (most recent call last):
  pulpcore-worker-4: File "/usr/lib/python3.6/site-packages/rq/worker.py", line 936, in perform_job
  .....
  pulpcore-worker-4: (max_doc_size, self.max_bson_size))
  pulpcore-worker-4: pymongo.errors.DocumentTooLarge: BSON document too large (32444638 bytes) - the connected server supports BSON document sizes up to 16777216 bytes.
  

Resolution

• This issue was reported under This content is not included.Bugzilla 2003888 and the behavior of the same has been greatly improved in Red Hat Satellite 6.9.8.

• A new This content is not included.Bugzilla has been opened as well to improve this behavior a bit more in Red Hat Satellite 6.9.8 and beyond.

• For the time being, It is suggested to upgrade to Red Hat Satellite 6.9.8 and then configure the PULP_CONTENT_PREMIGRATION_BATCH_SIZE as per the 3.1. Upgrading Satellite Server section of Satellite 6.10 upgrade guide.

  • A system with a slow I/O response may even need a value as low as 50 or 25 to be set or configured for PULP_CONTENT_PREMIGRATION_BATCH_SIZE.
  • While that could increase the time taken by the overall content migration process but at the same time, It should reduce the possibility of hitting the same issue a lot less frequently.

• It is additionally recommended to follow Pre-Migration Checks section from the upgrade guide to clean up unnecessary and unused contents from the Red Hat Satellite server.
  The more the amount of errata content to be migrated can be reduced, the fewer chances of running into this problem.

• If this issue persist on Red Hat Satellite 6.9.9 after reducing the PULP_CONTENT_PREMIGRATION_BATCH_SIZE to 25 then on Red Hat Satellite 6.9.9, following hotfix will help to fix the issue:

https://bugzilla.redhat.com/show_bug.cgi?id=2074099#c16

Hotfix RPM for Satellite 6.9.9

INSTALL INSTRUCTIONS:

1. Take a complete backup or snapshot of Satellite 6.9.9 server

2. Download the hotfix RPM attached to this BZ and copy it to Satellite server

3. # yum install ./python3-pulp-2to3-migration-0.11.10-2.HOTFIXRHBZ2074099RHBZ2038995.el7pc.noarch.rpm --disableplugin=foreman-protector

4. Then restart the satellite services with : satellite-maintain service restart

5. Then try migration.

Please reach out to This content is not included.Red Hat Technical Suppot in case of any further clarifications or support will be required.

For more KB articles/solutions related to Red Hat Satellite 6.x Pulp 3.0 Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Pulp 3.0-related Issues

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.