Bug 1151224
| Summary: | Warning in the log when starting celery services | ||
|---|---|---|---|
| Product: | [Retired] Pulp | Reporter: | Preethi Thomas <pthomas> |
| Component: | z_other | Assignee: | pulp-bugs |
| Status: | CLOSED UPSTREAM | QA Contact: | pulp-qe-list |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.4.1 | CC: | mhrivnak, rbarlow |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-28 22:39: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: | |||
|
Description
Preethi Thomas
2014-10-09 20:02:28 UTC
Here's the message with the log details removed:
/usr/lib/python2.7/site-packages/celery/apps/worker.py:161: CDeprecationWarning:
Starting from version 3.2 Celery will refuse to accept pickle by default.
The pickle serializer is a security concern as it may give attackers
the ability to execute any command. It's important to secure
your broker from unauthorized access when using pickle, so we think
that enabling pickle should require a deliberate action and not be
the default choice.
If you depend on pickle then you should set a setting to disable this
warning and to be sure that everything will continue working
when you upgrade to Celery 3.2::
CELERY_ACCEPT_CONTENT = ['pickle', 'json', 'msgpack', 'yaml']
You must only enable the serializers that you will actually use.
warnings.warn(CDeprecationWarning(W_PICKLE_DEPRECATED))
-------------- resource_manager.lab.eng.bos.redhat.com v3.1.11 (Cipater)
---- **** -----
I've added a troubleshooting note [0] to the 2.5.0 docs indicating this warning is part of normal operation. [0]: https://github.com/pulp/pulp/pull/1232 Putting this back to NEW because I only documented the bug I did not actually fix it. To fix this bug I think you will need to: - Port over all celery tasks to using arguments that serialize correctly with json - Have Pulp configure celery to disable all pickling except json - test test test and update the unit tests - Decide if the consumer agent executes arbitrary code passed in via the message bus, and if so if we are OK with that. If we are not then we need to start using the json serializer with consumer tasks also. Moved to https://pulp.plan.io/issues/575 |