Bug 1131251
Summary: | pulp-manage-db failures in 2.4 upgrade | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Pulp | Reporter: | Bryce Pier <bryce.pier> | ||||
Component: | z_other | Assignee: | Barnaby Court <bcourt> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Preethi Thomas <pthomas> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 2.4.0 | CC: | bcourt, mhrivnak, pthomas, rbarlow | ||||
Target Milestone: | --- | Keywords: | Triaged | ||||
Target Release: | 2.5.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-11-24 21:33: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: |
|
Description
Bryce Pier
2014-08-18 19:17:33 UTC
The odd thing is multiple runs of pulp-manage-db appeared to fix the problem. On the first few runs, the script would error out as mentioned above. Subsequent runs appeared to get farther (more repo.ids outputted before failure.) One later run, errored with: Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: Applying migration pulp_rpm.plugins.migrations.0016_new_yum_distribu short = pkglist.get('short') tor failed. Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: Link path [/var/lib/pulp/working/repos/rhel-5-x86_64-os/distributors/yum_distributor/repodata/productid.gz] exists, but is not a symbolic link Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: Traceback (most recent call last): Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/manage.py", line 86, in migrate_database Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: update_current_version=not options.test) Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrate/models.py", line 161, in apply_migration Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: migration.migrate() Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp_rpm/plugins/migrations/0016_new_yum_distributor.py", line 59, in migrate Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: _re_publish_repository(repo, d) Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp_rpm/plugins/migrations/0016_new_yum_distributor.py", line 165, in _re_publish_repository Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: publisher.publish() Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/plugins/util/publish_step.py", line 323, in publish Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: self.process_lifecycle() Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/plugins/util/publish_step.py", line 92, in process_lifecycle Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: step.process() Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/plugins/util/publish_step.py", line 150, in process Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: self._process_block() Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/plugins/util/publish_step.py", line 562, in _process_block Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: self.process_unit(package_unit) Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp_rpm/plugins/distributors/yum/publish.py", line 418, in process_unit Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: self._create_symlink(unit.storage_path, link_path) Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/plugins/util/publish_step.py", line 421, in _create_symlink Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: raise RuntimeError(msg % {'l': link_path}) Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: RuntimeError: Link path [/var/lib/pulp/working/repos/rhel-5-x86_64-os/distributors/yum_distributor/repodata/productid.gz] exists, but is not a symbolic link Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:CRITICAL: Aug 18 10:42:51 dvpuap02 pulp: pulp.server.db.manage:INFO: Database migrations complete. But then the next run of pulp-manage-db finished successfully and I was able to start the pulp_workers, etc. and connect to pulp via the admin client on the same VM. In all, I probably had to run pulp-manage-db 6-8 times for it to get all the way through the process. The first problem reported is because of None values stored for the package src attribute in the erratum unit or from attribute in the from section that was not being translated to an empty string for json serialization. build: 2.5.0-0.6.beta verified Upgraded from 2.3 ->2.5 with different types for content. pulp-manage-db ran without any errors |