origin: Command Line Tools not working on Ubuntu 18
Command Line Tools available on https://mirror.openshift.com/pub/openshift-v3/clients/3.11.0-0.21.0/linux/oc.tar.gz does not working on Ubuntu 18.
Version
3.11?
Steps To Reproduce
- Download https://mirror.openshift.com/pub/openshift-v3/clients/3.11.0-0.21.0/linux/oc.tar.gz
- Extract
- Try to run
oc <command>
Current Result
libcrypto.so.10: cannot open shared object file: No such file or directory
Expected Result
It should work.
Additional Information
The version from https://github.com/openshift/origin/releases/download/v3.10.0/openshift-origin-client-tools-v3.10.0-dd10d17-linux-64bit.tar.gz works on Ubuntu 18.
Current versions of libssl for Ubuntu 18
libssl1.0.0/bionic-updates,bionic-security,now 1.0.2n-1ubuntu5.1 libssl1.1/bionic-updates,bionic-security,now 1.1.0g-2ubuntu4.1
These versions are not compatible as far as I tested.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 11
- Comments: 34 (20 by maintainers)
For folks using OpenShift 4 during the preview/beta phase, @smarterclayton has also suggested https://artifacts-openshift-master.svc.ci.openshift.org/zips/ as a source of Ubuntu-compatible clients. Checking:
So that looks good compared to the most recent v4 build from the release page:
I’m not sure what the difference is in building that’s pulling in libcrypto or not.
@wangjun1974 I searched for package that provides
libcrypto.so.10and installed it.yum provides "*libcrypto.so.10"AND
yum install compat-openssl10I am hitting the same issue on both 16.04 and 18.04. This is a blocker. Symlink does not work as mentioned above:
The solution above yum provides “*libcrypto.so.10”
AND
yum install compat-openssl10
works on RHEL8
#22595 is the short-term fix for this, so folks with subsequent builds should be fine. The next step is to do something smart with
dlopenso folks can opt-in to a system libcrypto without requiring everyone to have the same system libcrypto, but users that don’t care one way or the other can probably stop worrying about this issue now. Not sure if that means “close this bug” or not 😉.It has to do with the FIPS mode crypto behavior in fedora/rhel golang. Still being worked on - it should have been using dlopen instead of a shared library. We will either disable it or fix it before the next drop.
On Fri, Mar 8, 2019 at 3:29 PM Jose Quaresma notifications@github.com wrote:
Yes, within the standard +/-1 version drift between client and server.
If I create a symlink to use these versions it fails because the headers aren’t compatible. My guess Ubuntu has a newer version and
ocuses an older one.