The GitHub Actions job "Tests (AMD)" on airflow.git/1fanwang/aip97-failure-details has succeeded. Run started by GitHub user 1fanwang (triggered by 1fanwang).
Head commit for run: 8ae4f32a3a9152cd32bacae03d67a7ba8ada3121 / 1fanwang <[email protected]> Classify control-plane pod disruptions as infra A node drain and a scheduler preemption are infrastructure taking the pod away, but Airflow reported both to the listener as an application failure and refunded nothing. Verified live on a k8s v1.35.0 cluster: both reach phase=Failed with pod.status.reason empty and the container reading only Error/exit 143, so neither the pod reason nor the container reason can see them. The signal lives in pod.status.conditions[type=DisruptionTarget], which the control plane sets before the delete and which survives onto the terminal object. Read that condition in collect_pod_failure_details and check it first in classify_pod_failure. Gated on status "True", matching Kubernetes' own podFailurePolicy matcher, since the writers update the condition in place. Signed-off-by: 1fanwang <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/30520019939 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
