Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
An unknown error is reported when you attempt to perform the following operations on a Red Hat Enterprise Linux 8.0 host: Upload a virtual machine to vSphere. Download a virtual machine from vSphere. Import an OVA or OVF file into Workstation Pro. Export a virtual machine to an OVA or OVF file
Version-Release number of selected component (if applicable):
8.0, 8.1
How reproducible:
100%
Steps to Reproduce:
1. Install rhel8 by default
2. Install Workstation 15.1 on rhel8
3. Open a terminal and try typing 'ovftool -v'
OR:
4. Launch Workstation and try to import/export/upload/download VM
Actual results:
After step 3, /usr/lib/vmware-ovftool/ovftool.bin: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory.
After step 4, it prompted 'unknown error'. Workstation UI told the user to check ovftool log, but no ovftool log was existing for ovftool was not loaded.
Expected results:
No error happened.
Additional info:
1) After I manually installed the libnsl package(libnsl-2.28-42.el8.x86_64.rpm) on rhel8.0 host os, ovftool loaded successfully, upload/download and import/export VM also succeeded.
2) I noticed another libnsl2-1.2.0-2.20180605git4a062cf.el8.x86_64 was installed by default, but it did not work with ovftool.
3) Vmware has an internal bug 2339061 to track this issue.
In my case, I was trying to perform a vCenter Server Appliance 6.0 - 6.5 upgrade from a Fedora 29 workstation and was getting the following in both the GUI and CLI VCSA Installer:
error: probeOvf unexpected error: Error: Invalid XML: <data>
-----
While trying to run the ovftool from the vSphere ISO (VMware-VCSA-all-6.5.0-14020092.iso), I discovered the same "libnsl.so.1: cannot open shared object file: No such file or directory" error.
Fedora 29 has libnsl2-1.2.0, which contains /usr/lib64/libnsl.so.2.0.0, and older versions are not available.
I was able to work around the "Invalid XML" and .so errors by symlinking /usr/lib64/libnsl.so.2.0.0 to /tmp/vcsa/libnsl.so.1 then running the GUI VCSA Installer as follows:
cd /mnt/tmp00/vcsa-ui-installer/lin64/
/mnt/tmp00/vcsa-ui-installer/lin64/
LD_LIBRARY_PATH=/tmp/vcsa ./installer
YMMV
I believe this is an ovftool issue as it doesn't package itself in a proper rpm, therefore unless the installer ensures the dependencies are present, it has no way to know if the necessary depedencies are present. In my opinion its an improvement as unnecessary packages shouldn't be loaded by default.
I think the comment #5 is correct, we should not change packages set that are installed by default, just to make software that does not handle dependencies properly working. I'm closing this bug NOTABUG now.