[Jadu07]

When execution_api_server_url was moved from [workers] to [core], the transition lacked a backward-compatibility deprecation mapping in parser.py.

As a result, Airflow 3 SDK ignores user configurations still placed under [workers], falling back to an often unresolvable Default URL derived from api.base_url. This caused Task SDK pods to crash on startup with an httpcore.ConnectError and prevented the task's hostname from being properly reported, resulting in Invalid URL log fetch errors in the UI.

This commit adds execution_api_server_url to deprecated_options to restore proper fallback behavior.

closes: #63945

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
• Google DeepMind for verification of the changes made.

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[Jadu07]

Hello sir @eladkal @gopidesupavan , please review this PR?

[Lee-W]

it was there since 3.0.0. I'm not sure why it relates to #63945

[Jadu07]

it was there since 3.0.0. I'm not sure why it relates to #63945

Thank you for catching this! You are absolutely right that execution_api_server_url has been in [core] since 3.0.0.

However, because the deprecation mapping in parser.py was never added back then, any legacy configuration still pointing to [workers] is silently ignored, leading to the broken log symptoms reported in #63945.
I have amended the PR to use version 3.0 instead to accurately reflect this.

[jason810496]

it was there since 3.0.0. I'm not sure why it relates to #63945

So do I, deprecating the [core/execution_api_server_url] doesn't seem to help resolve #63945.

[Jadu07]

it was there since 3.0.0. I'm not sure why it relates to #63945

So do I, deprecating the [core/execution_api_server_url] doesn't seem to help resolve #63945.

PR #46969 moved this from [workers] to [core] across multiple executors and the Helm chart, but missed this deprecation shim.

Without it, legacy [workers] configs are ignored, causing the ConnectError and the NULL hostname leading to the log fetch error in #63945.

[Lee-W]

Could you help clarify why we should support this? Airflow 2 to 3 may be one of the limited opportunities we have to remove elements we don’t intend to keep.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.