apache/airflow

Pod name incorrect in RenderedTaskInstanceFields

Open

#28.186 aperta il 7 dic 2022

Vedi su GitHub
 (9 commenti) (0 reazioni) (0 assegnatari)Python (16.781 fork)batch import
good first issuekind:documentationprovider:cncf-kubernetes

Metriche repository

Star
 (44.809 star)
Metriche merge PR
 (Merge medio 7g 18h) (834 PR mergiate in 30 g)

Descrizione

Apache Airflow version

2.5.0

What happened

  1. Start a task running with KubernetesExecutor
  2. Open the /rendered-k8s?dag_id=...&task_id=... endpoint in the web UI
  3. Copy the metadata.name
  4. kubectl logs pod/$name
  5. Error from server (NotFound): pods "example-sla-dag-sleep-20-1bc7f8d6892849eaac4642c4177e2eab" not found

By inspecting the

What you think should happen instead

Pod name presented in Rendered K8s Pod Spec should match the pod name used for running task. Otherwise pod name should not be presented at all.

This is not only a problem for users of the UI, also in the code it can be useful to have the real pod-id. I'm in the process of troubleshooting strange errors with task adoption, where there are frequently orphaned tasks found. Currently there appears to be no way to go from TI to pod_id, the adoption-process instead goes the other way, using pod labels to find TIs. So for any TIs that were not found in the adoption, one can not find if they at any point have had matching pods or not.

How to reproduce

No response

Operating System

Ubuntu 22.04

Versions of Apache Airflow Providers

No response

Deployment

Other Docker-based deployment

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Guida contributor