Update of vCenter from 8.0u2x to 8.0 U3x fails around 91% with 'Exception occurred in postInstallHook for content-library:Patch'

Products

• VMware vCenter Server

Issue/Introduction

Update of vCenter from 8.0u2x to 8.0 U3x fails around 91% with 'Exception occurred in postInstallHook for content-library:Patch'

• Option to Resume vCenter update fails and error repeats if attempted.
• In the /var/log/vmware/applmgmt/PatchRunner.log we see entries similar to below

 

content-library:Patch INFO cis_register Using key store name: machine
content-library:Patch ERROR vmware_b2b.patching.executor.hook_executor Patch hook 'content-library:Patch' failed.
Traceback (most recent call last):
File "/storage/updatemgr/software-updateq1mj18b8/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor.py", line 74, in executeHook
executionResult = systemExtension(args)
File "/storage/updatemgr/software-updateq1mj18b8/stage/scripts/patches/libs/sdk/extensions.py", line 106, in __call__
result = self.extension(*args)
File "/storage/updatemgr/software-updateq1mj18b8/stage/scripts/patches/libs/sdk/extensions.py", line 123, in _function

patch_errors.ComponentError
2025-10-07T21:01:47.589Z WARNING root stopping status aggregation...
2025-10-07T21:01:47.590Z ERROR __main__ Patch vCSA failed
(END)

Environment

vCenter Server 8.0.3

Cause

vCenter was part of ELM Mode

The vCenter upgrade process attempts to create the com.vmware.Content.Registry.Admin role, but it already exists in the vSphere environment, leading to a conflict.

This can happen if the role was manually created or retained from a previous vCenter version.

Resolution

Modify or add the missing configurations in vCenter

1. Log in to the vSphere Web Client 
2. Navigate to the Single Sign-On section under Administration.
3. Go to Roles and check if 'com.vmware.Content.Registry.Admin' exists.
4. Check for "Content Library Registry Administrator"
   
    
   
   
5. Click on Edit and type "com.vmware.Content.Registry.Admin". on the blank box 
6. Click on Save
7. Now you can see "Content Library Registry Administrator" changes to (sample) Example: Content Library Registry Administrator (sample) 
8. Now stop and restart all the vCenter Services  (service-control --stop --all && service-control --start --all)
9. Login to VAMI and reperform the upgrade.