Fix scheduler callback bundle_version when versioning disabled#66485
Merged
ephraimbuddy merged 1 commit intoMay 7, 2026
Merged
Conversation
When a DAG has disable_bundle_versioning=True, dag_run.bundle_version is left None at trigger time, but DagVersion.bundle_version still records the bundle SHA captured during DAG parse. Scheduler-emitted task callbacks (zombie tasks, heartbeat timeouts, stuck-in-queued) sourced bundle_version from DagVersion, so the DFP would check out a pinned versions/<sha>/ working tree and write a _tracking lockfile for a SHA the run was never pinned to — causing the callback to run against different code than the task itself, leaving per-version checkouts on disk, and blocking stale bundle cleanup. Source bundle_version from dag_run.bundle_version so the callback inherits the same unpinned state as the run and executes against the same on-disk code the task did.
boring-cyborg
Bot
added
the
area:Scheduler
ephraimbuddy
added
the
backport-to-v3-2-test
eladkal
approved these changes
May 6, 2026
Contributor
eladkal
left a comment
eladkal
left a comment
There was a problem hiding this comment.
Thank you @ephraimbuddy for this fix
feluelle
approved these changes
May 7, 2026
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
May 7, 2026
…abled (apache#66485) When a DAG has disable_bundle_versioning=True, dag_run.bundle_version is left None at trigger time, but DagVersion.bundle_version still records the bundle SHA captured during DAG parse. Scheduler-emitted task callbacks (zombie tasks, heartbeat timeouts, stuck-in-queued) sourced bundle_version from DagVersion, so the DFP would check out a pinned versions/<sha>/ working tree and write a _tracking lockfile for a SHA the run was never pinned to — causing the callback to run against different code than the task itself, leaving per-version checkouts on disk, and blocking stale bundle cleanup. Source bundle_version from dag_run.bundle_version so the callback inherits the same unpinned state as the run and executes against the same on-disk code the task did. (cherry picked from commit 38a51dc) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
May 7, 2026
…abled (apache#66485) When a DAG has disable_bundle_versioning=True, dag_run.bundle_version is left None at trigger time, but DagVersion.bundle_version still records the bundle SHA captured during DAG parse. Scheduler-emitted task callbacks (zombie tasks, heartbeat timeouts, stuck-in-queued) sourced bundle_version from DagVersion, so the DFP would check out a pinned versions/<sha>/ working tree and write a _tracking lockfile for a SHA the run was never pinned to — causing the callback to run against different code than the task itself, leaving per-version checkouts on disk, and blocking stale bundle cleanup. Source bundle_version from dag_run.bundle_version so the callback inherits the same unpinned state as the run and executes against the same on-disk code the task did. (cherry picked from commit 38a51dc) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
potiuk
pushed a commit
that referenced
this pull request
May 10, 2026
…abled (#66485) When a DAG has disable_bundle_versioning=True, dag_run.bundle_version is left None at trigger time, but DagVersion.bundle_version still records the bundle SHA captured during DAG parse. Scheduler-emitted task callbacks (zombie tasks, heartbeat timeouts, stuck-in-queued) sourced bundle_version from DagVersion, so the DFP would check out a pinned versions/<sha>/ working tree and write a _tracking lockfile for a SHA the run was never pinned to — causing the callback to run against different code than the task itself, leaving per-version checkouts on disk, and blocking stale bundle cleanup. Source bundle_version from dag_run.bundle_version so the callback inherits the same unpinned state as the run and executes against the same on-disk code the task did. (cherry picked from commit 38a51dc) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
potiuk
pushed a commit
that referenced
this pull request
May 10, 2026
…abled (#66485) (#66518) When a DAG has disable_bundle_versioning=True, dag_run.bundle_version is left None at trigger time, but DagVersion.bundle_version still records the bundle SHA captured during DAG parse. Scheduler-emitted task callbacks (zombie tasks, heartbeat timeouts, stuck-in-queued) sourced bundle_version from DagVersion, so the DFP would check out a pinned versions/<sha>/ working tree and write a _tracking lockfile for a SHA the run was never pinned to — causing the callback to run against different code than the task itself, leaving per-version checkouts on disk, and blocking stale bundle cleanup. Source bundle_version from dag_run.bundle_version so the callback inherits the same unpinned state as the run and executes against the same on-disk code the task did. (cherry picked from commit 38a51dc) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a DAG has disable_bundle_versioning=True, dag_run.bundle_version is left None at trigger time, but DagVersion.bundle_version still records the bundle SHA captured during DAG parse. Scheduler-emitted task callbacks (zombie tasks, heartbeat timeouts, stuck-in-queued) sourced bundle_version from DagVersion, so the DFP would check out a pinned versions// working tree and write a _tracking lockfile for a SHA the run was never pinned to — causing the callback to run against different code than the task itself, leaving per-version checkouts on disk, and blocking stale bundle cleanup.
Source bundle_version from dag_run.bundle_version so the callback inherits the same unpinned state as the run and executes against the same on-disk code the task did.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 4.7