github-actions[bot] opened a new pull request, #65616:
URL: https://github.com/apache/airflow/pull/65616
On ARM CI runners with a cold containerd cache, the first test in the K8s
system suite that needs the xcom sidecar image (alpine) or the basic_pod
template's image can exceed KubernetesPodOperator's 120s startup budget,
producing a PodLaunchTimeoutException that surfaces as a generic
"AirflowException: Pod ... returned a failure".
Two changes:
- basic_pod.yaml / test_full_pod_spec now use `ubuntu` instead of `perl`.
The pod only runs `/bin/bash -c 'echo ... > /airflow/xcom/return.json'`,
so any image with bash works, and `ubuntu` is already warmed by earlier
tests in the same suite — no extra image pull needed.
- Every real-cluster test that sets `do_xcom_push=True` now passes
`startup_timeout_seconds=XCOM_STARTUP_TIMEOUT_SECONDS` (300s). Since
pytest ordering is not guaranteed, whichever xcom test runs first has to
absorb the one-time alpine sidecar pull; bumping the budget on all of
them keeps the suite order-independent.
Observed failure: apache/airflow actions run 24716106401, job 72301089157
(K8S System:CeleryExecutor-3.12-v1.32.8-false, ARM). Both failing tests
took exactly ~120s matching the default startup_timeout_seconds; pod
events showed "Pulling image 'alpine' ..." with no "Successfully pulled"
inside the 120s window.
No production code change — the operator default of 120s is unchanged.
(cherry picked from commit 25f07dce44b620b97757d00a24c4d2e36bf1a5a2)
Co-authored-by: Jarek Potiuk <[email protected]>
--
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]
