Fix FAB DB manager discovery in migration-only contexts by Subham-KRLX · Pull Request #64145 · apache/airflow

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Subham-KRLX · 2026-03-24T07:37:29Z

This PR fixes a bug where the FABDBManager is not automatically discovered during database migrations in lean environments, such as the Helm migrateDatabaseJob.In these contexts (e.g., worker/migration containers), the call to
create_auth_manager().get_db_manager() in RunDBManager can fail because it may require an application context or runtime state that is not present. Previously, this failure was unhandled, causing the FABDBManager to be skipped and results in missing FAB tables (like ab_user, ab_role) unless manually configured.

This change wraps the fallback auth manager check in a try...except block, ensuring the migration process correctly uses the FABDBManager discovered via ProvidersManager which is the reliable discovery path in these environments.

closes: #63847

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

Yes — Gemini (Code Research and PR Description)

github-actions · 2026-03-24T13:33:00Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 2563e07 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

) Co-authored-by: Subham <subhamsangwan26@gmail.com>

Fix FAB DB manager discovery in migration-only contexts
52dacdd

eladkal added this to the Airflow 3.1.9 milestone Mar 24, 2026

eladkal added type:bug-fix Changelog: Bug Fixes backport-to-v3-1-test labels Mar 24, 2026

eladkal requested a review from vincbeck March 24, 2026 07:41

vincbeck approved these changes Mar 24, 2026
View reviewed changes

vincbeck merged commit 2563e07 into apache:mainMar 24, 2026
416 of 419 checks passed

vatsrahul1001 pushed a commit that referenced this pull request Mar 25, 2026
Fix FAB DB manager discovery in migration-only contexts (#64145)
de360fc

aaron-y-chen pushed a commit to aaron-y-chen/airflow that referenced this pull request Mar 30, 2026
Fix FAB DB manager discovery in migration-only contexts (apache#64145)
f099c1a

Suraj-kumar00 pushed a commit to Suraj-kumar00/airflow that referenced this pull request Apr 7, 2026
Fix FAB DB manager discovery in migration-only contexts (apache#64145)
09427c8

abhijeets25012-tech pushed a commit to abhijeets25012-tech/airflow that referenced this pull request Apr 9, 2026
Fix FAB DB manager discovery in migration-only contexts (apache#64145)
a1a2a9d

potiuk added the backport-to-v3-2-test label Apr 26, 2026

potiuk modified the milestones: Airflow 3.1.9 (never release), Airflow 3.2.2 Apr 26, 2026

potiuk mentioned this pull request Apr 26, 2026
[v3-2-test] Fix FAB DB manager discovery in migration-only contexts (#64145) #65894
Merged

potiuk added a commit that referenced this pull request Apr 26, 2026
Fix FAB DB manager discovery in migration-only contexts (#64145) (#65894
6a15b9a
) Co-authored-by: Subham <subhamsangwan26@gmail.com>

vatsrahul1001 pushed a commit that referenced this pull request Apr 27, 2026
Fix FAB DB manager discovery in migration-only contexts (#64145) (#65894
3040961
) Co-authored-by: Subham <subhamsangwan26@gmail.com>

vatsrahul1001 pushed a commit that referenced this pull request May 20, 2026
Fix FAB DB manager discovery in migration-only contexts (#64145) (#65894
44b1c48
) Co-authored-by: Subham <subhamsangwan26@gmail.com>

vatsrahul1001 mentioned this pull request May 21, 2026
Status of testing of Apache Airflow 3.2.2rc3 #67282
Closed