You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
used airflow.defaultSecurityContext.fsGroup: 0 without setting any other securityContext
followed the "how to persist logs" doc
result: No problem in airflow pods but KubernetesExecutorPods can't write to the logs volume
Relevant Logs
2023-04-05T02:46:39.148471134Z stderr F PermissionError: [Errno 1] Operation not permitted: '/opt/airflow/logs/dag_id=xxx/run_id=manual__2023-04-05T02:46:26.041418+00:00/task_id=xxx_01'
@obeyda this failure is caused by a bug in airflow itself that was introduced in version 2.5.1 (and is still present in 2.5.2, and 2.5.3), see here apache/airflow#29112. The problem is that Azure File does not allow chmod, and airflow mistakenly tries to run chmod on log files if they are not already 777.
For now, you might want to do one of the following:
This issue has been automatically marked as stale because it has not had activity in 60 days.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.
Issues never become stale if any of the following is true:
Checks
User-Community Airflow Helm Chart
.Chart Version
8.6.1
Kubernetes Version
Helm Version
Description
airflow.defaultSecurityContext.fsGroup: 0
without setting any othersecurityContext
result: No problem in airflow pods but KubernetesExecutorPods can't write to the logs volume
Relevant Logs
2023-04-05T02:46:39.148471134Z stderr F PermissionError: [Errno 1] Operation not permitted: '/opt/airflow/logs/dag_id=xxx/run_id=manual__2023-04-05T02:46:26.041418+00:00/task_id=xxx_01'
Custom Helm Values
The text was updated successfully, but these errors were encountered: