potiuk commented on issue #34644: URL: https://github.com/apache/airflow/issues/34644#issuecomment-1856081623
The lack of more details seems to be because the message is not coming from airflow but from the POD. The message is "just" displayed by the airflow's KPO and the error is somewhere on the POD. There are likely two ways you can address your problem @tommyhutcheson: * if you can upgrade to the latest version of Kubernetes Provider then you have a chance that a) problem has been fixed there b) logging will be more comprehensive. You are using pretty old version of the provider (7.3.0) where 7.11.0 is already available and there were numerous improvements and bugfixes implemented there See the https://airflow.apache.org/docs/apache-airflow-providers-cncf-kubernetes/stable/changelog.html . One of the changes implemented in 7.7.0 for example improved multi-line handling of logs by KPO https://github.com/apache/airflow/pull/34412 but there were many more and if you want to be more certain if you should upgrade, I recommend you to go and read in detail the changelog. Each change there contains reference to PR# and you can find and look at the PR where you will find detailed description of all the changes - since it is an open-source project and all is "in the clear". * Another option is to take a look at the detailed logs of your k8s Pods that are failing. I do not know KPO that well and what kind of flexibility the K8S interface Composer gives you, but I believe you can set KPO in the mode that it wil not be clearing PODs immediately after running and you will be able to inspect much more information - seems you recognize the need of having more detailed information what's going on, so if you would like to analyse it in detail before upgrading, it's likely the way to go. However, I'd urge you to upgrade everything you can first. Many of our users experience problems that have long been solved and in this case there are quite many issues implemented since your version. You can either attempt it in the way that you want to be sure that you should upgrade (in which case I advise you to do detailed analysis of the changelog) or **just upgrade** and see if you still experience the problem. The latter is usually faster, and takes less time - both for you and volunteers here who have no time to go through detailed list of changelog just to make sure partcular problems have been fixed. This is an open-source project, so people here help when they have time (they are not paid for it) and in cases like that, it's quite a bit on the user to make sure to make the effort to ugprade to latest version in case they experience problems in later versions - especially in case there were many fixes since. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
