Actions
Issue #1065
closedTask #1014: Short Term Improvements for Pulp's use of MongoDB
DeprecationWarning on pulp-manage-db
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.7.0 Beta
Platform Release:
2.7.0
OS:
RHEL 6
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
>> rpm -qa|grep mongoe
python-mongoengine-0.7.10-2.el6.noarch
>> rpm -qa pulp-server
pulp-server-2.7.0-0.3.beta.el6.noarch
>> sudo -u apache pulp-manage-db
Mongo database for connection is version 2.4.13
Loading content types.
Loading type descriptors [rpm_support.json, puppet.json, iso_support.json]
Parsing type descriptors
Validating type descriptor syntactic integrity
Validating type descriptor semantic integrity
Updating the database with types [distribution, drpm, erratum, package_group, package_category, package_environment, rpm, srpm, yum_repo_metadata_file, puppet_module, iso]
/usr/lib/python2.6/site-packages/pulp/server/db/connection.py:167: DeprecationWarning: The safe parameter is deprecated. Please use write concern options instead.
return method(*args, **kwargs)
Content types loaded.
Ensuring the admin role and user are in place.
Admin role and user are in place.
Beginning database migrations.
Migration package pulp.server.db.migrations is up to date at version 18
Migration package pulp_puppet.plugins.migrations is up to date at version 2
Migration package pulp_rpm.plugins.migrations is up to date at version 21
Database migrations complete.
Related issues
Updated by rbarlow about 9 years ago
This actually happens in all of our processes, not just pulp-manage-db. If we decide to move away from Mongo, we won't need to solve this issue. If we decide to stay with Mongo, we will need to start using write concerns instead of the safe argument.
Updated by igulina@redhat.com about 9 years ago
- OS changed from RHEL 7 to RHEL 6
Updated by bmbouter about 9 years ago
- Blocks Issue #974: GET of a task sometimes 404s on first request added
Updated by bmbouter about 9 years ago
- Blocked by Issue #1139: Fix Pulp's use of replica sets replica sets added
Updated by amacdona@redhat.com almost 9 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to amacdona@redhat.com
- Platform Release set to 2.7.0
Added by Austin Macdonald almost 9 years ago
Added by Austin Macdonald almost 9 years ago
Updated by amacdona@redhat.com almost 9 years ago
- Status changed from ASSIGNED to POST
Added by Austin Macdonald almost 9 years ago
Revision 8ec9c6b7 | View on GitHub
remove safe=true
re #1065
Updated by amacdona@redhat.com almost 9 years ago
Added by Austin Macdonald almost 9 years ago
Revision cc59c50a | View on GitHub
rm safe=true
re #1065
Added by Austin Macdonald almost 9 years ago
Revision 55fc57b0 | View on GitHub
remove safe=true
re #1065
Updated by amacdona@redhat.com almost 9 years ago
Updated by Anonymous almost 9 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|c904e5f3dea37207fd4645a7df817fe49d2f377f.
Updated by dkliban@redhat.com almost 9 years ago
- Status changed from MODIFIED to 5
Updated by amacdona@redhat.com almost 9 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
rm safe=true
Remove the deprecated safe=True from all calls to PyMongo.
closes #1065