-
Notifications
You must be signed in to change notification settings - Fork 7
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
vnet-manager installation fails on Ubuntu 20.04 due to old pyopenssl #60
Comments
Output from
I wouldn't consider myself to be a Python expert, but I think all of this boils down to a compatibility issue between |
The requests issue should be fixed in release 1.1.1 with PR #61 I cannot reproduce the openssl issue. I tried to make a fresh install on Ubuntu 20.04 with Py3.8 and the latest packages.
The |
Thanks for your reply! I've used this image: https://cloud-images.ubuntu.com/focal/current/ -> focal-server-cloudimg-amd64-disk-kvm.img On a fresh install (you might have used a different image!), these packages are installed:
Installing Now... after installing Co-installing Apparently, we should not use You have added requests as a requirement, but the version constraints will not prevent a Re-installed the guest yet another time. After applying this change: diff --git a/requirements/base.txt b/requirements/base.txt
index def0384..2bb889c 100644
--- a/requirements/base.txt
+++ b/requirements/base.txt
@@ -5,4 +5,4 @@ pylxd>=2.3.1
pyroute2==0.7.3
psutil>=5.9.0
distro>=1.7.0
-requests<2.30.0
+requests>=2.24.0,<2.30.0
Conclusion
Either we remove support for focal, we ask people to uninstall (using apt) or upgrade (using pip3) python3-openssl/PyOpenSSL on focal systems before installing vnet-manager on focal, we introduce a hard dependency on PyOpenSSL with a proper version constraint, or we ask the pylxd developers to incorporate a fix in their requirements file. What do you think? |
Based on issues seen in #60 Recomment to use venv
Thanks for the explanation @Southparkfan, I see now that this is an issue with system packages interfering with the setup. I updated the README to recommend people to install vnet-manager in a virtualenv now (at least on older OS'es). |
Hi Erik,
Nice to meet you. You're an alumnus of OS3, I'm a new student 👋
We're using vnet-manager in our labs, in Ubuntu 20.04 VMs. Unfortunately, I've had to deal with a bug during initial setup of vnet-manager. TL;DR there is a workaround (upgrading pyopenssl).
I have installed a clean VM:
(+ https://github.com/Erik-Lamers1/vnet-manager#install-the-required-packages)
Running
pip3 install vnet-manager
:vnet-manager
cannot be executed:This error was fixed by reinstalling pyopenssl (cf. https://stackoverflow.com/a/75295873). In yet another clean VM I have verified running
pip3 install pyopenssl --upgrade
(upgrade to v23.3.0) before installing vnet-manager also fixes the issue. focal's python3-openssl package is based on v19.0.0, which is too old.On top of this, I had encountered another error during topology creation (
TypeError: request() got an unexpected keyword argument 'chunked'
), which I fixed by installingrequest==2.28.0
, but I couldn't reproduce this bug... probably interesting for later.The text was updated successfully, but these errors were encountered: