-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Unknown error in KubernetesJobWatcher. Failing #33066
Comments
Unfortunately the exception information is swallowed. Is it possible that you find this line:
In kubernetes_executor_utils and replace it with
That should give use more clues. |
done that but doesn't seem like much changed:
here's what it says with that change:
it looks like the same thing to me, maybe I have done the wrong change somewhere? |
I think this issue has been reported long time ago and happened in past versions of k8s, you can try to find similar issues - kubernetes-client/python#972 is one of them but there are a number of related. From a quick search it does not seem that issue had any reasonable resolution, but my best guess and suggestion to you @karakanb will be to upgrade to latest k8s version. 1.27 has .4 version currently - not sure if that will help but there is a chance it will.. |
I am already on 1.27.2 and the issue is still there unfortunately. I guess this has nothing to do with Airflow then, I'll close the issue. |
same issue here with kube 1.26.11 and airflow 2.7.0. |
same issue here as well with kube 1.28.5 and airflow 2.8.2. Is there any configuration variable which i can change? |
i'm with kube v1.29.4 and airflow 2.8.2 |
Apache Airflow version
2.6.3
What happened
I regularly see these logs in my scheduler logs every 10 minutes:
Not sure about the implications of this but I see these logs every time I need to investigate things, which makes it harder to debug issues. In the best case this is not really an issue and makes debugging hard, in the worst case it causes some issue that I haven't been able to identify yet.
What you think should happen instead
There should be no such log, this seems like an unexpected behavior.
How to reproduce
Deploy the official helm chart v1.9.0 using the following values file:
Operating System
Debian GNU/Linux 11 (bullseye)
Versions of Apache Airflow Providers
apache-airflow-providers-amazon==8.1.0
apache-airflow-providers-celery==3.2.1
apache-airflow-providers-cncf-kubernetes==7.4.0
apache-airflow-providers-common-sql==1.6.1
apache-airflow-providers-discord==3.2.0
apache-airflow-providers-docker==3.7.1
apache-airflow-providers-elasticsearch==4.5.1
apache-airflow-providers-ftp==3.4.2
apache-airflow-providers-google==10.5.0
apache-airflow-providers-grpc==3.2.1
apache-airflow-providers-hashicorp==3.4.1
apache-airflow-providers-http==4.4.2
apache-airflow-providers-imap==3.2.2
apache-airflow-providers-microsoft-azure==6.1.2
apache-airflow-providers-mysql==5.1.1
apache-airflow-providers-odbc==4.0.0
apache-airflow-providers-postgres==5.5.1
apache-airflow-providers-redis==3.2.1
apache-airflow-providers-sendgrid==3.2.1
apache-airflow-providers-sftp==4.3.1
apache-airflow-providers-slack==7.3.2
apache-airflow-providers-snowflake==4.4.0
apache-airflow-providers-sqlite==3.4.2
apache-airflow-providers-ssh==3.7.1
apache-airflow-providers-tableau==4.2.0
Deployment
Official Apache Airflow Helm Chart
Deployment details
Kubernetes v1.27.2
Anything else
LIterally every 10 minutes:
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: