Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Repeated warnings about MongoClient opening before fork, while syncing content.
Version-Release number of selected component (if applicable):
SNAP5
How reproducible:
Unsure
Steps to Reproduce:
1. Begin syncing a number of custom products. In this case, I was syncing all three EPEL repos for each of RHEL 5-7.
2. View /var/log/messages
Actual results:
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672) /usr/lib64/python2.7/site-packages/pymongo/topology.py:74: UserWarning: MongoClient opened before fork. Create MongoClient with connect=False, or create client after forking. See PyMongo's documentation for details: http://api.mongodb.org/python/current/faq.html#using-pymongo-with-multiprocessing>
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672) "MongoClient opened before fork. Create MongoClient "
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672)
Mar 29 15:15:32 rhsm-qe-3 pulp: celery.worker.job:INFO: Task pulp.server.controllers.repository.queue_download_deferred[f8cc4a44-ae7a-449b-8cac-3f01d45d1f21] succeeded in 0.0531026830431s: None
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672) /usr/lib/python2.7/site-packages/mongoengine/queryset/base.py:461: DeprecationWarning: update is deprecated. Use replace_one, update_one or update_many instead.
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672) upsert=upsert, **write_concern)
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672)
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672) /usr/lib/python2.7/site-packages/mongoengine/document.py:367: DeprecationWarning: update is deprecated. Use replace_one, update_one or update_many instead.
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672) upsert=upsert, **write_concern)
Mar 29 15:15:32 rhsm-qe-3 pulp: py.warnings:WARNING: (6841-72672)
[This message gets repeated from time to time.]
Expected results:
Probably shouldn't be seeing this. But it is a warning.
Additional info:
This is on a box that was recently rebooted, so it probably isn't a symptom of the presently known pulp degradation issue.
To clarify, I don't think, but I am not sure, that this is causing any problems. I wrote it up because 1) we've never seen this message and 2) in case it helps root out any other unknown pulp issues.
This issue is already tracked in pulp's redmine:
https://pulp.plan.io/issues/1580
The short version of this issue is that the warnings can be ignored, and connecting before forking is not causing any problems. While I was able to put together some code to suppress the warnings, the solution wasn't reliable enough and was rejected.
Comment 5pulp-infra@redhat.com
2016-04-14 19:27:49 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2016-04-14 19:27:52 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.