Skip to content
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

Breaks production Docker image: Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow #9193

Closed
dinigo opened this issue Jun 9, 2020 · 3 comments
Labels
kind:bug This is a clearly a bug

Comments

@dinigo
Copy link
Contributor

dinigo commented Jun 9, 2020

Hello. We are experiencing some issues in local development due to a celery using a module that it doesn't install anymore.

This happened when upping dependency version of celery 4.4.3 to 4.4.4

Apache Airflow version: 2.0 - Official docker image (apache/airflow:master)

What happened:

Commit aa89900 updated celery 4.4.3 to 4.4.4 with the bug reported in here celery/celery#6145. Celery 4.4.4 depends on future but doesn't require it.

All of our local environments are failing

What you expected to happen:
Restore celery=4.4.3 in the requirements files and rebuild the dockerhub images

How to reproduce it:
Start the image normally

Anything else we need to know:
MicrosoftTeams-image

@dinigo dinigo added the kind:bug This is a clearly a bug label Jun 9, 2020
@dinigo dinigo changed the title Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow Breaks production Docker image: Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow Jun 9, 2020
@potiuk
Copy link
Member

potiuk commented Jun 9, 2020

Fixed in #9194 - the images should rebuild tonight (we have nightly builds) and they should contain celery 4.4.5

@potiuk potiuk closed this as completed Jun 9, 2020
@dinigo
Copy link
Contributor Author

dinigo commented Jun 10, 2020

Thanks a lot @potiuk and @mik-laj! You saved my day :)

@potiuk
Copy link
Member

potiuk commented Jun 10, 2020

Glad it helped :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug This is a clearly a bug
Projects
None yet
Development

No branches or pull requests

2 participants