-
Notifications
You must be signed in to change notification settings - Fork 134
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
Amazon Linux 2023.6.20241212 Client() returns KeyError: http+unix #619
Comments
@Dweller can you identify what changed between the working version and the broken one? Please check |
The pylxd version if 2.3.5 (I've downgraded it to 2.5.1 with no difference in the result). I'll get a list of the depending packages later on.. I'm assuming its probably going to be urllib3 which is where the error is being raised from.. Possibly because this latest version of Amazon linux has boosted the python version and supporting libs.. Will confirm later on today |
I've not yet been able to confirm the version changes but a quick web search how's its possible it was a change made to requests-unix-sockets.. Apparently they have no intention of fixing this one. |
OK so this if the installed python modules on Amazon Linux 2023.6.20241212 after doing a yum install python3-pip and then pip install pylxd. The python version is 3.9.20.
|
And the previous version.... that works.. Amazon Linux release 2023.6.20241121
|
Which is to say no difference what so ever..
|
Working version is running Broken version is Python 3.9.20 Is biggest difference I can find so far.. |
Ok I've resolved the issue with pylxd by installing python3.12 on the platform... So my conclusion is the issue is connected with python3.9.20 |
My ec2 nodes pylxd scripts don't work with the latest version of Amazon Linux 2023.6.20241212
Client()call returns KeyError: http+unix which is to day almost like the underlining module doesn't understand http+unix?.
If I go back a version of Amazon Linux then it still works with exactly the same cloud-init configuration.
However if I issue a curl request to the same port..
The text was updated successfully, but these errors were encountered: