raphaelauv edited a comment on issue #22485:
URL: https://github.com/apache/airflow/issues/22485#issuecomment-1076257110
I can't reproduce with
airflow `2.2.2` - `apache-airflow-providers-cncf-kubernetes==3.1.1,`
or
`2.2.4` - `apache-airflow-providers-cncf-kubernetes==3.1.1,`
the operator can re-attach the running pod if I restart the sceduler
```log
[2022-03-23, 11:22:27 UTC] {kubernetes_pod.py:525} INFO - Creating pod
airflow-test-pod.9a94208666254a0099f44c2ce811c62e with labels: {'dag_id':
'kubernetes_dag', 'task_id': 'task-one', 'run_id':
'scheduled__2022-03-13T0000000000-eef165281', 'try_number': '4'}
[2022-03-23, 11:22:27 UTC] {kubernetes_pod.py:336} INFO - Found matching pod
airflow-test-pod.485275d944964e8188c0db5f10776956 with labels
{'airflow_version': '2.2.2', 'dag_id': 'kubernetes_dag',
'kubernetes_pod_operator': 'True', 'run_id':
'scheduled__2022-03-13T0000000000-eef165281', 'task_id': 'task-one',
'try_number': '3'}
[2022-03-23, 11:22:27 UTC] {kubernetes_pod.py:337} INFO - `try_number` of
task_instance: 4
[2022-03-23, 11:22:27 UTC] {kubernetes_pod.py:338} INFO - `try_number` of
pod: 3
```
could you give us more context on the KPO ( what kind of K8S it use,
in_cluster ? ... ) and the FULL airflow logs of the error
--
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]
