Fix lang-SDK k8s system test dropping the api-server auth manager#69221
Merged
Conversation
… manager The lang-SDK coordinator system test provisioning helm-upgrades the already-deployed Airflow release with only the lang-SDK values file. Because the upgrade did not reuse the release's existing values, Helm re-rendered from chart defaults and discarded the base deploy's --set overrides -- including config.core.auth_manager, which the base deploy sets to SimpleAuthManager on Python 3.13 (FAB does not support 3.13). The api-server then came back up on the chart-default FabAuthManager and never wrote simple_auth_manager_passwords.json.generated, so every API-login test in the KubernetesExecutor-3.13 variant errored with FileNotFoundError while fetching the generated admin password. Reuse the existing release's values on the lang-SDK upgrade so the overrides layer on top and the auth manager (and the rest of the base configuration) stays intact.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
potiuk
added
the
all versions
eladkal
approved these changes
Jul 1, 2026
bugraoz93
approved these changes
Jul 1, 2026
Contributor
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker bfba4eb v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
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.
The
KubernetesExecutor-3.13k8s system test job started failing on mainafter #68709 with 9
FileNotFoundError: /tmp/simple_auth_manager_passwords.json.generatederrors (every API-login test), e.g.
https://github.com/apache/airflow/actions/runs/28526595970/job/84584069072
Root cause: the lang-SDK provisioning (
breeze k8s setup-lang-sdk-test)helm-upgrades the already-deployed release with only
lang_sdk/config/values.yaml.Without
--reuse-values, Helm re-renders from chart defaults and drops the basedeploy's
--setoverrides — notablyconfig.core.auth_manager=SimpleAuthManager(set on Python 3.13, where FAB is unavailable). The api-server reverts to the
chart-default
FabAuthManagerand never writes the generated password file thetests fetch.
Fix: add
--reuse-valuesso the lang-SDK values layer on top of the existingrelease instead of replacing it — matching the intent (the same PR already made
dagBundleConfigListadditive for exactly this reason).The change is only exercised by the K8s system test job itself (no unit-test
harness exists for these breeze helm-command builders), so verification is that
job going green.
related: #68709
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8 1M) following the guidelines