Update to VMware vCenter Server 7.0U3o is failing due to an RPM dependency

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Patching vCenter Server to 7.0U3o failed with the error "Installation of one or more RPMs failed"

• The below error is seen in the update_microservice.log:
  Log path: /var/log/vmware/applmgmt/update_microservice.log

Updating / installing...
bash-4.4.18-4.ph3 ########################################
Cleaning up / removing...
bash-4.4.18-2.ph3 ########################################
][/bin/sh: error while loading shared libraries: libtinfo.so.6: cannot open shared object file: No such file or directory
warning: %postun(bash-4.4.18-2.ph3.x86_64) scriptlet failed, exit status 127

• Source vCenter was applied patch in the past.

Environment

VMware vCenter Server 7.0.3

Cause

The problem stems from a bash-rpm update in 7.0U3o, causing a regression in the vCenter 7.0U3o branch.

Resolution

• The issue is fixed in vSphere 7.0U3p version

Workaround:

There are multiple workarounds available, please choose the most viable path depending on your use case.

In case the update is not performed yet, apply one of the below workaround proactively to avoid failure.
If the failure has occurred already, revert the failed setup to a previously working VC version, and try any of the below workarounds.

Option1:
Apply an intermediate patch to 7.0U3i before updating to 7.0U3o.

 1. Revert the failed vCSA to a previously working version.
 2. Perform an update to an intermediate version (7.0U3i) through VAMI or API.
 3. Perform an update to 7.0U3o through the preferred mechanism (VAMI, API, CLI).

Option 2:
Use VAMI UI to perform the update, by calling Stage and Install operations separately.

 1. Revert the failed vCSA to a previously working version.
 2. Login into VAMI UI.
 3. Select the 'STAGE' option from the VAMI UI.
 4. Select the 'INSTALL' option from the VAMI UI.

Option 3:
Clean the stale Patching.db file available on the vCSA before starting the update.

 1. Revert the failed vCSA to a previously working version
 2. SSH into the vCSA server using root credentials.
 3. Delete the stale Patching.db file from vCSA.
  ○ mv /storage/db/patching.db /storage/db/patching.db.old
 4. Perform an update to 7.0U3o through the preferred mechanism (VAMI, API, CLI).