-
Notifications
You must be signed in to change notification settings - Fork 135
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
pylxd
broken by dependency requests
2.32.0
#579
Labels
Comments
1 task
I proposed a fix in msabramo/requests-unixsocket#72 |
+1 It also affects the self-hosted runners https://github.com/canonical/github-runner-operator using local LXD (a freshly packed charm cannot be installed anymore). |
@simondeziel can we pin our deps in this repo for time being? |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like the latest minor version release of the
requests
package breaks pylxd if you are communicating with the LXD API via the unix socket on the host. Here's the link to the issue: psf/requests#6707requests
now checks the scheme of the URL being used to communication with an endpoint; it does not recognize the http+unix scheme used to communicate with the LXD unix socket, so it throws an error when we attempt to contact LXD. Here's the error the HPC team is currently seeing in our CI when we attempt to pre-configure LXD before deploying Juju applications:Workarounds
Looks like we'll either need to pin the version of requests to < 2.32 or find a workaround that enables pylxd to still communicate in HTTP over the LXD API unix socket.
requests_unixsocket
isn't pinned to a specific version ofrequests
, so it will bring in the latest version ofrequests
regardless.The text was updated successfully, but these errors were encountered: