Bug 1404348

Summary: pulp_rpm migration 0031 fails: cursor not found
Product: Red Hat Satellite Reporter: Dennis Kliban <dkliban>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: high Docs Contact:
Priority: high    
Version: UnspecifiedCC: bbuckingham, bkearney, bmbouter, cwelton, daviddavis, dkliban, ggainey, ipanova, jcallaha, mhrivnak, pcreech, rchan, rplevka, satellite6-bugs, ttereshc, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: UnusedFlags: rplevka: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pulp-rpm-2.8.7.7-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1417111 (view as bug list) Environment:
Last Closed: 2017-03-06 08:35:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1417111    

Description Dennis Kliban 2016-12-13 16:08:17 UTC
I am migrating our production pulp instance from 2.7 to 2.10.

The data migration (triggered by pulp-manage-db) failed:

Applying migration pulp_rpm.plugins.migrations.0031_regenerate_repo_unit_counts failed.

Halting migrations due to a migration failure.
Cursor not found, cursor id: 102945255089
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 194, in main
    return _auto_manage_db(options)
  File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 257, in _auto_manage_db
    migrate_database(options)
  File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 124, in migrate_database
    update_current_version=not options.test)
  File "/usr/lib/python2.7/site-packages/pulp/server/db/migrate/models.py", line 186, in apply_migration
    migration.migrate()
  File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/migrations/0031_regenerate_repo_unit_counts.py", line 48, in migrate
    for repo in repos_collection.find():
  File "/usr/lib64/python2.7/site-packages/pymongo/cursor.py", line 1114, in next
    if len(self.__data) or self._refresh():
  File "/usr/lib64/python2.7/site-packages/pymongo/cursor.py", line 1056, in _refresh
    self.__max_await_time_ms))
  File "/usr/lib64/python2.7/site-packages/pymongo/cursor.py", line 926, in __send_message
    codec_options=self.__codec_options)
  File "/usr/lib64/python2.7/site-packages/pymongo/helpers.py", line 123, in _unpack_response
    raise CursorNotFound(msg, 43, errobj)
CursorNotFound: Cursor not found, cursor id: 102945255089



The migration was added as part of 2.8.5 Pulp. This bug will be experienced by users with a large number of repositories.

Comment 1 pulp-infra@redhat.com 2016-12-13 16:42:07 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 2 pulp-infra@redhat.com 2016-12-13 16:42:09 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.

Comment 4 pulp-infra@redhat.com 2016-12-16 14:01:10 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.

Comment 5 pulp-infra@redhat.com 2016-12-16 15:32:42 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

Comment 6 pulp-infra@redhat.com 2016-12-16 18:11:57 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 7 pulp-infra@redhat.com 2016-12-16 18:31:07 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 8 pulp-infra@redhat.com 2017-01-10 02:01:41 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 9 pulp-infra@redhat.com 2017-01-16 21:01:57 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 11 Roman Plevka 2017-02-20 13:40:03 UTC
I believe this bug is not supposed to be verified by satellite6 QA?

Comment 14 errata-xmlrpc 2017-03-06 08:35:47 UTC
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:0447