Fix: Pin urllib3 version in logs-deploy.sh 49/73649/2 v0.92.5
authorAnil Belur <abelur@linuxfoundation.org>
Wed, 24 Sep 2025 12:25:33 +0000 (22:25 +1000)
committerAnil Belur <abelur@linuxfoundation.org>
Wed, 24 Sep 2025 12:35:23 +0000 (22:35 +1000)
commit463db44214f6a7f23fe1df66d75ce66f73f00005
tree4ad828929d83e19f27efa8761efb00b2fdee57c4
parent05c8bc21a55d90fe327add099a51819fa74b42b6
Fix: Pin urllib3 version in logs-deploy.sh

This patch pins urllib3~=1.26.15 in logs-deploy.sh script to fix
S3 upload timeout errors. Jobs were failing with
"urllib3.exceptions.ReadTimeoutError" and
"botocore.exceptions.ReadTimeoutError" when uploading large log
files to S3.

The error occurs because newer urllib3 versions (>=2.0.0) have
incompatible timeout handling with boto3/botocore used for
S3 uploads. This change makes logs-deploy.sh consistent with
other scripts in global-jjb that already pin urllib3 to v1.26.15.

Error:
TimeoutError: _ssl.c:989: The handshake operation timed out
urllib3.exceptions.ReadTimeoutError: AWSHTTPSConnectionPool(host='
odl-logs-s3-cloudfront-index.s3.us-west-1.amazonaws.com', port=443):
Read timed out. (read timeout=60) botocore.exceptions.ReadTimeoutErr:
Read timeout on endpoint URL: "https://odl-logs-s3-cloudfront-
index.s3.us-west-1.amazonaws.com/logs/releng/vex-yul-odl-jenkins-1/
controller-maven-verify-master-mvn39-openjdk21/3193/
_build-details.log.gz"

Issue: IT-28722
Change-Id: Iaf5818063d645994c4aa1b1f002e53ef2661d418
Signed-off-by: Anil Belur <abelur@linuxfoundation.org>
releasenotes/notes/pin-urllib3-logs-deploy-script-0a21b684fc35d28e.yaml [new file with mode: 0644]
shell/logs-deploy.sh