-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Log server on celery worker does not work in IPv6-only setup #24755
Comments
Would you like to fix it - you seem to know, where and how and you have nice environment to test the fix in. And you will not have to wait for someone to pick it up - this is one of the best ways you can contribute back to the software you get for free and join the community of more than 2100 contributors. |
-- edited -- Hi @potiuk, I'll try to craft a PR, thanks for the inspiration :) I have one question, maybe you can help or point me to the right source: Answer: Look in the documentation for building the image and there for section building from github.
What I tried before: I did a tiny code change (hardcoded the log server to some other number,
But this builds from the latest pypi version of airflow, doh. When I deployed an image built with the that command with a helm chart to our Kubernetes Cluster nothing changed and my code change was not visible of course. |
Yeah. This is good observation. The If you are curious - you might run it with |
Apache Airflow version
2.2.5
What happened
I deployed the Airflow helm chart in a Kubernetes cluster that only allows IPv6 traffic.
When I want to look at a task log in the UI there is this message:
So the webserver cannot fetch the logfile from the worker.
This happens in my opinion because the gunicorn application listens to
0.0.0.0
(IPv4), see code or worker log below, and the inter-pod communication in my cluster is IPv6.What you think should happen instead
The gunicorn webserver should (configurably) listen to IPv6 traffic.
How to reproduce
No response
Operating System
Debian GNU/Linux 10 (buster)
Versions of Apache Airflow Providers
No response
Deployment
Other 3rd-party Helm chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: