-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu 22.04 - Release 20250214.2.0 - Failing to install python packages #11611
Comments
Hi @sbonds - Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating. |
My workaround was to use ubuntu 20.04. I removed the workaround since I noticed in issue #11602 that there was a solution to try. So far, all of my pipeline run attempts with "ubuntu-latest" are getting the 20250209.1.0 image. I'm not sure if this was the fix or if I'm just having "bad" luck in getting this known-good image. I guess the good news is that |
I'm still only getting 20250209.1.0 runners so I can't confirm that a newer runner version works. |
Hi @sbonds - Kindly try to run the pipeline with new rollout and confirm ? |
Runner image version 20250223.1.0 fails with the same error message. |
This seems to be an issue with pip 22.0.2. If I update to pip 25.0.1, it works. I also tested with pip 22.0.2 at a user-level install just in case there was something special with a non-system-level pip install, and pip 22.0.2 also failed in that config. This also seems to be specific to an URL-based pip install. When I use the system pip 22.0.2 to install mkdocs via "pip install mkdocs==1.6.1" it works fine. |
Description
When by sheer luck I get 20250209.1.0 as my runner, everything works fine.
This appears very similar to existing issue #11602 but my error message is slightly different so I thought I would open a new issue rather than possibly confusing the troubleshooting in issue 11602.
Pipeline YAML
This is a demonstration pipeline so it's intentionally very simple, which makes troubleshooting that much simpler too. That first
pip install https://github.com/mkdocs/mkdocs/archive/refs/tags/1.6.1.tar.gz
fails.Error message
The fatal error is
Preparing metadata (pyproject.toml): finished with status 'error'
due toModuleNotFoundError: No module named 'packaging.licenses'
. The complete step log is below under "actual behavior".Platforms affected
Runner images affected
Image version and build link
Image: ubuntu-22.04
Version: 20250214.2.0
Raw log from Initialize Job
This is the relevant section from that log, but is not the complete log:
Is it regression?
https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20250209.1
Expected behavior
This is the log from the mkdocs install during a working run:
Actual behavior
The pip process fails with
Preparing metadata (pyproject.toml): finished with status 'error'
due toModuleNotFoundError: No module named 'packaging.licenses'
Repro steps
Create a pipeline running the "ubuntu-latest" running which uses a pip install command like
pip install https://github.com/mkdocs/mkdocs/archive/refs/tags/1.6.1.tar.gz
Run the pipeline. If you randomly get a runner version
20250214.2.0
it will fail. If you get20250209.1.0
it will succeed.The text was updated successfully, but these errors were encountered: