-
Type:
Build Failure
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Infrastructure
-
None
-
Python Drivers
-
Not Needed
-
-
None
-
None
-
None
-
None
-
None
-
None
Name of Failure:
uv install fails during setup on gcpkms/azurekms remote test hosts due to missing pip
Link to task:
Context of when and why the failure occurred:
The test-gcpkms task in the mongo-python-driver project failed during setup on 2026-08-03. The task provisions a fresh GCE instance, then clones drivers-evergreen-tools and runs its setup, which calls ensure_uv() to bootstrap the uv tool. On this host, the system Python has no pip module, and the ensurepip fallback did not recover it, so ensure_uv() could not install uv and setup.sh aborted before any tests ran. The same gap applies to the analogous azurekms remote host.
This is a regression introduced by DRIVERS-3564, which replaced the prior filesystem scan for a usable Python interpreter with ensure_uv(). The new path requires pip (or an already-installed uv) to bootstrap uv, a dependency the old approach never needed, and the gcpkms/azurekms remote provisioning scripts were not updated to install it.
Stack trace:
uv not found on PATH; installing with 'python3 -m pip install --user uv'... /usr/bin/python3: No module named pip /usr/bin/python3: No module named pip ERROR: could not find or install uv. Install it manually, then re-run: https://docs.astral.sh/uv/getting-started/installation/ If you believe uv/pip should already be available in this environment, please file a ticket in the DEVPROD Jira project: https://jira.mongodb.org/projects/DEVPROD ERROR Command '['./setup.sh']' returned non-zero exit status 1. error: recipe setup-tests failed on line 93 with exit code 1
- is caused by
-
DRIVERS-3564 Migrate drivers-evergreen-tools Python dependency management to a uv workspace with a single lock file
-
- In Review
-