KKHYeon opened a new issue, #38246: URL: https://github.com/apache/airflow/issues/38246
### Apache Airflow version Other Airflow 2 version (please specify below) ### If "Other Airflow 2 version" selected, which one? 2.6.3 ### What happened?  All dag runs were failed 1. This was happened only CeleryExecutor not KubernetesExecutor 2. There is no attempt1.log but exist attept2.log ``` [2024-03-16T01:36:02.637+0000] {taskinstance.py:1093} INFO - Dependencies not met for <TaskInstance: [DAG_ID]__2024-03-14T15:01:00+00:00 [failed]>, dependency 'Task Instance State' FAILED: Task is in the 'failed' state. [2024-03-16T01:36:02.650+0000] {local_task_job_runner.py:154} INFO - Task is not able to be run [2024-03-16T01:36:02.871+0000] {taskinstance.py:1093} INFO - Dependencies not met for <TaskInstance: [DAG_ID]__2024-03-14T15:01:00+00:00 [failed]>, dependency 'Task Instance State' FAILED: Task is in the 'failed' state. [2024-03-16T01:36:02.935+0000] {local_task_job_runner.py:154} INFO - Task is not able to be run ``` 3. scheduler error log ``` ERROR - Executor reports task instance <TaskInstance: [DAG_ID] scheduled__2024-03-14T15:01:00+00:00 [queued]> finished (failed) although the task says its queued. (Info: None) Was the task killed externally? ``` 4. after all components restarted, the tasks are succeed ### What you think should happen instead? _No response_ ### How to reproduce I don't know ### Operating System PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
