oguzhangur96 commented on issue #30991:
URL: https://github.com/apache/airflow/issues/30991#issuecomment-1830061373
We have faced a similar issue (with the same error) and found out that our
local logging folder owner user is **root** but the user
`apache/airflow:slim-2.7.3-python3.10` image uses to write the logs is
**airflow** .
This results seeing a log like `*** No logs found in GCS; ti=%s
<TaskInstance: mydag.my_task manual__2023-05-01T12:25:55.937029+00:00` from
the logs tab of task UI but after checking the scheduler logs we found out that
scheduler was unable to write the logs to local folder. This results empty logs
at GCS, since logs are written to GCS after task completion and task is failed
because it can't write logs.
You can change the owner of local logs directory to user **airflow** or if
you are using kubernetes (deploying without helm) and mounting a persistent
volume you can add below setting to your _deployment.yaml_ which makes user
**airflow** owner of mounted volume directories.
```
securityContext:
fsGroup: 50000
```
I guess, this should not happen if you are using [official helm
chart](https://airflow.apache.org/docs/helm-chart/stable/index.html).
--
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]
