Upgrade to VCD 10.6 GA fails with error regarding Failed dependencies.

Products

• VMware Cloud Director

Issue/Introduction

While trying to perform an upgrade of VMware vCloud Director to version 10.6, error is received related to the below dependencies.

/opt/likewise/bin/domainjoin-cli: error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory
/opt/likewise/bin/domainjoin-cli: error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory
/opt/likewise/bin/lwsm: error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory
Removed /etc/systemd/system/multi-user.target.wants/lwsmd.service.
28/06/2024 13:30:39 [INFO] Update status: Done pre-install scripts
28/06/2024 13:30:39 [INFO] Update status: Running installation tests
28/06/2024 13:30:39 [INFO] Running /opt/vmware/var/lib/vami/update/data/job/21/test_command
warning: /opt/vmware/var/lib/vami/update/data/package-pool/package-pool/audit-2.8.5-31.ph4.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 8a6a826d: NOKEY
warning: /opt/vmware/var/lib/vami/update/data/package-pool/package-pool/vmware-vcloud-distribution-ovascripts-10.6.0-24055916.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 530c79e6: NOKEY
error: Failed dependencies:
 libcrypto.so.1.0.0()(64bit) is needed by (installed) xml-security-c-1.7.3-4.ph2.x86_64
 libssl.so.1.0.0()(64bit) is needed by (installed) xml-security-c-1.7.3-4.ph2.x86_64

Environment

VMware Cloud Director 10.4
VMware Cloud Director 10.5
VMware Cloud Director 10.6

Cause

xml-security-c-1.7.3-4.ph2.x86_64 package is installed. It is a photon OS 2.0 package.

The above package is causing the upgrade to fail.

Resolution

1.    Please check if the above package is installed in the environment by executing the command 

rpm -qa | grep xml-security-c

2.    If the above package is available, remove the package by executing the below command

rpm -e xml-security-c-1.7.3-4

3.    Once the package is removed, proceed with the upgrade.