tanvn commented on issue #26623:
URL: https://github.com/apache/airflow/issues/26623#issuecomment-1301770702
I found that all the error workers failed to mount some configmaps, as the
events on all the failed pods is showing as below:
```Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 5m default-scheduler
Successfully assigned betadailyclientupdater-e2f8afd8a2374d1bab3dbb7485af76f2
to lniudtk1613
Normal Pulled 4m57s kubelet Container
image "abc/airflow-core-242:latest" already present on machine
Normal Created 4m56s kubelet Created
container base
Normal Started 4m56s kubelet Started
container base
Warning FailedMount 4m49s (x2 over 4m50s) kubelet
MountVolume.SetUp failed for volume "config" : object "airflow-airflow-config"
not registered
Warning FailedMount 4m49s (x2 over 4m50s) kubelet
MountVolume.SetUp failed for volume "krb5-keytab-volume" : object
"airflow-default-keytab" not registered
Warning FailedMount 4m49s (x2 over 4m50s) kubelet
MountVolume.SetUp failed for volume "kube-api-access-9gsv6" : object
"kube-root-ca.crt" not registered
Warning FailedMount 4m49s (x2 over 4m50s) kubelet
MountVolume.SetUp failed for volume "krb5-config-volume" : object
"airflow-default-krb5-configmap" not registered
------
```
and this is happening randomly.
Confirmed that the `"airflow-airflow-config" ` configmap is created and
available but somehow can not be mounted.
So I started to think that it is an error related to the k8s cluster on
which my Airflow is running, not Airflow 2.4.2 itself.
--
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]
