Fix LatestBoto CI stuck at boto3 1.38.2 (below provider minimum)#68122
Merged
Conversation
shahar1
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-2-test
1 task
The `check_boto_upgrade()` function in `entrypoint_ci.sh` was capping boto3/botocore at `<1.38.3` to prevent urllib3 2.6.0 from being pulled in (it had removed `getheaders()`, breaking the kubernetes client). That workaround was applied in Dec 2025 alongside a `urllib3<2.6.0` pin. Since then, urllib3 2.6.1+ restored `getheaders()`, and the other affected files (`kubernetes-tests/pyproject.toml`, `providers/cncf/kubernetes/pyproject.toml`) were already updated to `urllib3!=2.6.0` (PR apache#59203). The `entrypoint_ci.sh` was missed. Result: the LatestBoto CI job was installing boto3 1.38.2, which is below the amazon provider's declared minimum (`boto3>=1.41.0`) and predates the addition of the `bedrock-agentcore-control` and `bedrock-agentcore` services to botocore, causing unrelated test failures for new operators that use those services. Fix: remove the boto3/botocore upper bounds and change `urllib3<2.6.0` to `urllib3!=2.6.0`, consistent with the rest of the repo.
shahar1
force-pushed
the
fix/latest-boto-urllib3-constraint
branch
from
28987cc to
320b66e
Compare
eladkal
approved these changes
Jun 6, 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
Jun 6, 2026
…der minimum) (apache#68122) The `check_boto_upgrade()` function in `entrypoint_ci.sh` was capping boto3/botocore at `<1.38.3` to prevent urllib3 2.6.0 from being pulled in (it had removed `getheaders()`, breaking the kubernetes client). That workaround was applied in Dec 2025 alongside a `urllib3<2.6.0` pin. Since then, urllib3 2.6.1+ restored `getheaders()`, and the other affected files (`kubernetes-tests/pyproject.toml`, `providers/cncf/kubernetes/pyproject.toml`) were already updated to `urllib3!=2.6.0` (PR apache#59203). The `entrypoint_ci.sh` was missed. Result: the LatestBoto CI job was installing boto3 1.38.2, which is below the amazon provider's declared minimum (`boto3>=1.41.0`) and predates the addition of the `bedrock-agentcore-control` and `bedrock-agentcore` services to botocore, causing unrelated test failures for new operators that use those services. Fix: remove the boto3/botocore upper bounds and change `urllib3<2.6.0` to `urllib3!=2.6.0`, consistent with the rest of the repo. (cherry picked from commit a4ea3ff) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Jun 6, 2026
…der minimum) (apache#68122) The `check_boto_upgrade()` function in `entrypoint_ci.sh` was capping boto3/botocore at `<1.38.3` to prevent urllib3 2.6.0 from being pulled in (it had removed `getheaders()`, breaking the kubernetes client). That workaround was applied in Dec 2025 alongside a `urllib3<2.6.0` pin. Since then, urllib3 2.6.1+ restored `getheaders()`, and the other affected files (`kubernetes-tests/pyproject.toml`, `providers/cncf/kubernetes/pyproject.toml`) were already updated to `urllib3!=2.6.0` (PR apache#59203). The `entrypoint_ci.sh` was missed. Result: the LatestBoto CI job was installing boto3 1.38.2, which is below the amazon provider's declared minimum (`boto3>=1.41.0`) and predates the addition of the `bedrock-agentcore-control` and `bedrock-agentcore` services to botocore, causing unrelated test failures for new operators that use those services. Fix: remove the boto3/botocore upper bounds and change `urllib3<2.6.0` to `urllib3!=2.6.0`, consistent with the rest of the repo. (cherry picked from commit a4ea3ff) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
shahar1
added a commit
that referenced
this pull request
Jun 6, 2026
…der minimum) (#68122) (#68128) The `check_boto_upgrade()` function in `entrypoint_ci.sh` was capping boto3/botocore at `<1.38.3` to prevent urllib3 2.6.0 from being pulled in (it had removed `getheaders()`, breaking the kubernetes client). That workaround was applied in Dec 2025 alongside a `urllib3<2.6.0` pin. Since then, urllib3 2.6.1+ restored `getheaders()`, and the other affected files (`kubernetes-tests/pyproject.toml`, `providers/cncf/kubernetes/pyproject.toml`) were already updated to `urllib3!=2.6.0` (PR #59203). The `entrypoint_ci.sh` was missed. Result: the LatestBoto CI job was installing boto3 1.38.2, which is below the amazon provider's declared minimum (`boto3>=1.41.0`) and predates the addition of the `bedrock-agentcore-control` and `bedrock-agentcore` services to botocore, causing unrelated test failures for new operators that use those services. Fix: remove the boto3/botocore upper bounds and change `urllib3<2.6.0` to `urllib3!=2.6.0`, consistent with the rest of the repo. (cherry picked from commit a4ea3ff) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.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
2 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
check_boto_upgrade()function inscripts/docker/entrypoint_ci.shwas cappingboto3/botocore at
<1.38.3to avoid urllib3 2.6.0 being pulled in (it had removedgetheaders(), breaking the kubernetes client).Since then:
getheaders()— the bug was only in exactly 2.6.0kubernetes-tests/pyproject.tomlandproviders/cncf/kubernetes/pyproject.tomlwerealready updated to
urllib3!=2.6.0(PR Convert the exclusion on urllib3 to != for 2.6.0 #59203)boto3>=1.41.0But
entrypoint_ci.shwas not updated, leaving the LatestBoto CI job installingboto3 1.38.2, which:
boto3>=1.41.0)bedrock-agentcore-control/bedrock-agentcoreservices being addedto botocore, causing spurious test failures for any operators that use those services
(e.g. PR Add Amazon Bedrock AgentCore Runtime operators #67984, spotted via run https://github.com/apache/airflow/actions/runs/27028907135/job/79778239095)
Change
Remove the
boto3<1.38.3/botocore<1.38.3upper bounds and changeurllib3<2.6.0→urllib3!=2.6.0, consistent with what the rest of the repoalready does.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Sonnet 4.6) following the guidelines