celery / celery

Distributed Task Queue (development branch)
https://docs.celeryq.dev
Other
24.64k stars 4.65k forks source link

Using new settings syntax result_backend does not work to replace CELERY_RESULT_BACKEND #7140

Open Antsthebul opened 2 years ago

Antsthebul commented 2 years ago

Checklist

Mandatory Debugging Information

Optional Debugging Information

Related Issues and Possible Duplicates

Related Issues

Possible Duplicates

Environment & Settings

Celery version:

celery report Output:

``` ```

Steps to Reproduce

Required Dependencies

Python Packages

pip freeze Output:

``` amqp==5.0.6 appnope==0.1.2 asgiref==3.3.4 async-generator==1.10 atomicwrites==1.4.0 attrs==21.2.0 backcall==0.2.0 billiard==3.6.4.0 boto3==1.18.52 botocore==1.21.52 celery==5.2.1 certifi==2021.5.30 cffi==1.14.5 charset-normalizer==2.0.4 click==8.0.3 click-didyoumean==0.3.0 click-plugins==1.1.1 click-repl==0.2.0 colorama==0.4.4 configparser==5.0.2 crayons==0.4.0 cryptography==3.4.7 decorator==5.0.9 Django==3.2.1 django-extensions==3.1.3 djangorestframework==3.12.4 djangorestframework-simplejwt==4.7.2 factory-boy==3.2.1 Faker==9.8.2 gunicorn==20.1.0 h11==0.12.0 idna==3.2 iniconfig==1.1.1 ipython==7.16.1 ipython-genutils==0.2.0 jedi==0.18.0 jmespath==0.10.0 kombu==5.2.2 numpy==1.21.4 outcome==1.1.0 packaging==21.2 parso==0.8.2 pexpect==4.8.0 pickleshare==0.7.5 pluggy==1.0.0 prompt-toolkit==3.0.18 ptyprocess==0.7.0 py==1.10.0 pycparser==2.20 Pygments==2.9.0 PyJWT==2.1.0 pyOpenSSL==21.0.0 pyparsing==2.4.7 pytest==6.2.5 pytest-django==4.4.0 python-dateutil==2.8.2 python-dotenv==0.19.0 pytz==2021.1 redis==3.5.3 requests==2.26.0 s3transfer==0.5.0 selenium==4.0.0 six==1.16.0 sniffio==1.2.0 sortedcontainers==2.4.0 sqlparse==0.4.1 stripe==2.63.0 text-unidecode==1.3 toml==0.10.2 traitlets==4.3.3 trio==0.19.0 trio-websocket==0.9.2 typing-extensions==3.10.0.0 urllib3==1.26.6 vine==5.0.0 wcwidth==0.2.5 webdriver-manager==3.5.1 wsproto==1.0.0 amqp==5.0.6 appnope==0.1.2 asgiref==3.3.4 async-generator==1.10 atomicwrites==1.4.0 attrs==21.2.0 backcall==0.2.0 billiard==3.6.4.0 boto3==1.18.52 botocore==1.21.52 celery==5.2.1 certifi==2021.5.30 cffi==1.14.5 charset-normalizer==2.0.4 click==8.0.3 click-didyoumean==0.3.0 click-plugins==1.1.1 click-repl==0.2.0 colorama==0.4.4 configparser==5.0.2 crayons==0.4.0 cryptography==3.4.7 decorator==5.0.9 Django==3.2.1 django-extensions==3.1.3 djangorestframework==3.12.4 djangorestframework-simplejwt==4.7.2 factory-boy==3.2.1 Faker==9.8.2 gunicorn==20.1.0 h11==0.12.0 idna==3.2 iniconfig==1.1.1 ipython==7.16.1 ipython-genutils==0.2.0 jedi==0.18.0 jmespath==0.10.0 kombu==5.2.2 numpy==1.21.4 outcome==1.1.0 packaging==21.2 parso==0.8.2 pexpect==4.8.0 pickleshare==0.7.5 pluggy==1.0.0 prompt-toolkit==3.0.18 ptyprocess==0.7.0 py==1.10.0 pycparser==2.20 Pygments==2.9.0 PyJWT==2.1.0 pyOpenSSL==21.0.0 pyparsing==2.4.7 pytest==6.2.5 pytest-django==4.4.0 python-dateutil==2.8.2 python-dotenv==0.19.0 pytz==2021.1 redis==3.5.3 requests==2.26.0 s3transfer==0.5.0 selenium==4.0.0 six==1.16.0 sniffio==1.2.0 sortedcontainers==2.4.0 sqlparse==0.4.1 stripe==2.63.0 text-unidecode==1.3 toml==0.10.2 traitlets==4.3.3 trio==0.19.0 trio-websocket==0.9.2 typing-extensions==3.10.0.0 urllib3==1.26.6 vine==5.0.0 wcwidth==0.2.5 webdriver-manager==3.5.1 wsproto==1.0.0 ```

Other Dependencies

N/A

Minimally Reproducible Test Case

```python ```

Expected Behavior

Result backend to be configured to the specified address.

Actual Behavior

The backend is configurable when either specifying the backend url in the Celery invocation, or using CELERY_RESULT_BACKEND. But if using CELERY_RESULT_BACKEND the warning


    version 6.0.0. Use the result_backend instead```

is displayed yet when switching settings to `result_backend` as recommended the result backend is not configured and registerted as disabled.
open-collective-bot[bot] commented 2 years ago

Hey @Antsthebul :wave:, Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider backing us - every little helps!

We also offer priority support for our sponsors. If you require immediate assistance please consider sponsoring us.

auvipy commented 2 years ago
version 6.0.0. Use the result_backend instead```

is displayed yet when switching settings to result_backend as recommended the result backend is not configured and registerted as disabled.

-- you get this even after using result_backend?

Antsthebul commented 2 years ago

When i switch to the recommended syntax the configured backend is not picked up

thedrow commented 2 years ago

I've seen this myself. I don't know what's wrong though.