potiuk commented on issue #18698: URL: https://github.com/apache/airflow/issues/18698#issuecomment-934648943
First of all description/title of the problem is wrong. There is no way UI error cause task failure, because there is no possibility of doing so. The logs suggest that you are mixing cause with resulr This is not a reproducible case - and it looks like this is a deployment issue. It looks like some of your workers do not properly set their name properly - likely hostname-callable does not return the right host name https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#hostname-callable (which would indicate temporary DNS problem in your Kubernetes). I'd recommend to follow: https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ More information is needed from various logs (including logs of what is happening in your Kubernetes when name resolution happens) is needed in order to make it qualifies as Airflow issue. Switching to discussion unless more information is provided. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
