rjgoyln opened a new pull request, #73034:
URL: https://github.com/apache/airflow/pull/73034
## Summary
Both task instance lookups in `KubernetesPodTrigger` build their error the
way a logging call is written — a `%s` template plus positional arguments — and
`AirflowException` performs no such substitution. The message therefore reaches
the user as the argument tuple, with the identifiers it exists to carry left
behind the placeholders:
```
('TaskInstance with dag_id: %s, task_id: %s, run_id: %s and map_index: %s is
not found', 'my_dag', 'my_task', 'manual__2026-05-21T00:00:00+00:00', 2)
```
- Both sites interpolate the four identifiers into one formatted message
- The Airflow 3 test asserts the whole message instead of a substring, which
is what fails without the fix
- The Airflow 2 lookup gets its own test, exercised by the 2.11
compatibility job
The same defect in the Google provider is out of scope here; #72697 covers
it.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 5)
Generated-by: Claude Code (Opus 5) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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]
