Bug 1110269
| Summary: | Migration from 2.2 to 2.3 fails during pulp-manage-db-run. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Pulp | Reporter: | akegata | ||||
| Component: | nodes | Assignee: | pulp-bugs | ||||
| Status: | CLOSED WONTFIX | QA Contact: | pulp-qe-list | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 2.3 | CC: | mhrivnak | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-06-18 16:41:21 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: | |||||||
| Attachments: |
|
||||||
Created attachment 909637 [details]
migration patch
I provided this patch to the OP, which should allow the migration to complete. I do not know how the database got to the current state.
The OP confirmed in IRC that the upgrade was actually from 2.1.3 to 2.3. This appears to be an unknown bug in the 2.1 importer (which no longer exists), causing a failure during upgrade to 2.2. There is a patch attached here that resolves the issue in case someone hits it again, but we are not going to issue a fix to this migration in a new release. |
Description of problem: I upgraded pulp from 2.2 to 2.3, and was prompted to dun pulp-manage-db. pulp-manage-db fails with "# pulp-manage-db Beginning database migrations. Migration package pulp.server.db.migrations is up to date at version 6 Migration package pulp_puppet.plugins.migrations is up to date at version 0 Applying pulp_rpm.migrations version 11 Applying migration pulp_rpm.migrations.0011_new_importer failed. See log for details. 2014-06-17 12:37:49,015 db:CRITICAL: Applying migration pulp_rpm.migrations.0011_new_importer failed. 2014-06-17 12:37:49,016 db:CRITICAL: 'repodata' 2014-06-17 12:37:49,017 db:CRITICAL: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pulp/server/db/manage.py", line 79, in migrate_database update_current_version=not options.test) File "/usr/lib/python2.6/site-packages/pulp/server/db/migrate/models.py", line 161, in apply_migration migration.migrate() File "/usr/lib/python2.6/site-packages/pulp_rpm/migrations/0011_new_importer.py", line 29, in migrate _migrate_collection(type_id) File "/usr/lib/python2.6/site-packages/pulp_rpm/migrations/0011_new_importer.py", line 39, in _migrate_collection text = package['repodata']['primary'].encode(codec) KeyError: 'repodata'" Version-Release number of selected component (if applicable): pulp-server-2.3.1-1.el6.noarch How reproducible: Unsure. It fails the same way every time I run pulp-manage-db, but I do not know if this is caused by one of my custom repos or something else. Steps to Reproduce: 1. Upgrade pulp to 2.3 2. Run pulp-manage-db Actual results: DB migration fails. Expected results: DB migration should succeed. Additional info: I've tried changing log level in /etc/pulp/logging/basic.cfg and /etc/pulp/logging/db.cfg, but I can't find a setting that gives me any more info than the above error message.