Closed obeyda closed 1 year ago
@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 https://github.com/apache/airflow/issues/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:
Azure Blob Storage
remote provider2.5.0
(but this is an older version, which might have separate problems).2.4.3
(but downgrading your DB might be problematic).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:
lifecycle/frozen
labelClosing because this is an upstream issue, your best bet is to NOT use Airflow 2.5.1
, 2.5.2
, or 2.5.3
(which all have this bug).
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
Custom Helm Values