Uh oh!
There was an error while loading. Please reload this page.
[v3-2-test] Fix LatestBoto CI test stuck at boto3 1.38.2 (below provider minimum) (#68122) - #68128
Merged
Merged
Conversation
…der minimum) (#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 #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>
1 task
shahar1
marked this pull request as ready for review
June 6, 2026 09:27
shahar1
requested review from
amoghrajesh, ashb, bugraoz93, gopidesupavan, jason810496, jscheffl and potiuk
as code ownersJune 6, 2026 09:27
jscheffl
approved these changes
Jun 6, 2026
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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 inentrypoint_ci.shwas capping boto3/botocoreat
<1.38.3to prevent urllib3 2.6.0 from being pulled in (it had removedgetheaders(), breaking the kubernetes client). That workaround was applied inDec 2025 alongside a
urllib3<2.6.0pin.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). Theentrypoint_ci.shwas 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 ofthe
bedrock-agentcore-controlandbedrock-agentcoreservices 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.0tourllib3!=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