-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
vine is not installed as part of the celery's requirements #3547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just tried to reproduce on a fresh virtual environment:
As you can see, |
I'm experiencing this now installing celery 4.0.2 in a Debian:jessie Docker container. What's happening for me is that certain dependencies are not being installed when I include celery as a dependency of a Django project (in the project's |
Just happened to me. We're building with
|
@malinoff Do you not think this worth re-opening? |
I'm willing to re-open and fix this issue, but only if I get the exact steps to reproduce, |
Ok, I did some more digging and in our case the problem was actually that we had been specifying an older version of kombu in our setup.py before we added celery, and due to a limitation in pip (pypa/pip#775), that conflict isn't detected and the older version was being installed instead of the one specified by celery. Sorry about that! |
running |
I ran into a similar problem by specifying an out-of-date version of |
This "problem" typically happens when people pin dependencies to some old package... |
Sorry, I didn't mean to indicate there was an issue here, just that I found the solution by reading this ticket and wanted to include the package that was causing my problem to help alleviate any future searcher's troubles. |
I'm getting this error in a Raspberry Pi 3. I guess it's consequence of the errors I get when installing. Doesn't install completely on a RPi3 |
I got this error:
|
Hello, today I had this issue with celery version 4.3.0 The problem was that celery was installing vine version 4.0.0 I think, but it works with version 1.3.0 |
Upgrade to 4.3.1. worked for me. |
This happened installing 5.0.0 on a fresh env as well |
Thanks. I can´t find your commit. Installing the dev version from master does not resolve this issue for me. |
So, now it worked. However it now fails due to "No module named 'celery.five'" |
The opensuse images tend to be less stable, and the opensuse nodeset was moved to openSUSE 15.2 which does not work properly with devstack for the train and lower branches. Ussuri works for the moment, and Victoria+ have been moved to Ubuntu, so this patch is targeted for stable/train and prior to disable voting for opensuse-based jobs. To fix the gate, patch also pulls in this backport: Update amqp lower constraint Newer versions of kombu rely on updated versions of amqp [0]. Keystone's lower-constraints job is failing consistently across multiple branches because it's referencing amqp 2.2.2 when we should be relying on a newer version (5.0.0+). You can verify this by using `pip3 check` with the lower-constraints tox environment. Without this patch, you'll likely see the test_notifications tests fail with something like: ModuleNotFoundError: No module named 'vine.five' Which spirals into subsequent failures mocking messaging drivers. [0] celery/celery#3547 (cherry picked from commit c495defc2bd4f2ef5a38d2a9e4d5aac5653fb406) (cherry picked from commit 12891a039fb1dae7ba22884cf78ad7d1faa8569d) (cherry picked from commit d435a915160a9876b58f2a04696d9430790e5cdc) Change-Id: I2895300556b83e943ce5e5fd72e4b86317a306a9
Newer versions of kombu rely on updated versions of amqp [0]. Keystone's lower-constraints job is failing consistently across multiple branches because it's referencing amqp 2.2.2 when we should be relying on a newer version (5.0.0+). You can verify this by using `pip3 check` with the lower-constraints tox environment. Without this patch, you'll likely see the test_notifications tests fail with something like: ModuleNotFoundError: No module named 'vine.five' Which spirals into subsequent failures mocking messaging drivers. This commit also fixes the lower-constraint for PyMySQL. keystone does not have any lower constraint for PyMySQL so the latest version 0.10.0 is picked by the job which is failing [1] In OpenStack, PyMySQL's upper constraint is 0.9.3. Version 0.10.0 is not tested [2]. Let's add PyMySQL lower constraint also so that we test lower-constraint job with correct lower version. Both of these fixes were proposed separate reviews in newer branches, but due to a circular failure, they're being proposed together. The amqp fix fails lower-constraints jobs because the PyMySQL issue and vice versa. [0] celery/celery#3547 [1]https://zuul.opendev.org/t/openstack/build/3077d96f4fff4b7985cb763d0635d471/log/job-output.txt#621 [2]https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L384 Change-Id: I3834b3b34641c006c70614d5331d292c41f8a346 Closes-Bug: #1888886 (cherry picked from commit c495defc2bd4f2ef5a38d2a9e4d5aac5653fb406) (cherry picked from commit 12891a039fb1dae7ba22884cf78ad7d1faa8569d) (cherry picked from commit b7c3458b6f11ade0ce54889ae5f782fbac4a9a2e) (cherry picked from commit 255b6cdd70db654ce8112cef0b86361c34d9993b) (cherry picked from commit 3de085b) (cherry picked from commit 300e79e) (cherry picked from commit fb7d545) (cherry picked from commit 32967a8105efd2a0934ab123eb10f33df7f581c5)
Checklist
celery -A proj report
in the issue.(if you are not able to do this, then at least specify the Celery
version affected).
master
branch of Celery.Steps to reproduce
pip install celery
Then in python:
from celery import Celery
Expected behavior
Celery running fine.
Actual behavior
The text was updated successfully, but these errors were encountered: