Patching vCenter to 8.0 Update 3e fails at 80% and fails when starting trustmanagement service.

Products

VMware vCenter Server

Issue/Introduction

When patching vCenter to 8.0 Update 3e 8.0.3.00500 24674346 patching may fail at stage 80% importing data.

In the Patchrunner.log located at /var/log/vmware/applmgmt you see the following error:

2025-06-04T09:22:56.291Z INFO service manager Starting service 'vmware-trustmanagement' 
2025-06-04T09:22:56.292Z INFO service manager Executing command '[['/bin/service-control' 
2025-06-04T09:25:59.385Z INFO service manager Command
Performing start operation on service trustmanagement...
'--start', *vmware-trustmanagement']]'
[['/bin/service-control', '--start', 'vmware-trustmanagement']]' has exit-code='1' and stdout: Operation not cancellable. Please wait for it to finish...
stderr: Error executing start on service trustmanagement. Details { "detail": [
{
}
1,
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '%(0)s'", "args": [
],
"trustmanagement"
"Localized": "An error occurred while starting service 'trustmanagement'"
"componentKey": null,
"problemId": null,
"resolution": null
Service-control failed. Error: {
"detail": [
1,
{
}
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '*(0)s'", "args": [
"trustmanagement"
1, "Localized": "An error occurred while starting service 'trustmanagement"
"componentKey": null,
"problemId": null,

In the trustmanagement-svcs.log located at /var/log/vmware/trustmanagement you see the following:

Caused by: com.vmware.identity.interop.NativeCallException: Native platform error [code: 40712][null][null]
        at com.vmware.identity.interop.registry.RegistryAdapter.checkNativeErrorCode(RegistryAdapter.java:1334) ~[vmware-identity-platform.jar:?]
        at com.vmware.identity.interop.registry.RegistryAdapter.openKey(RegistryAdapter.java:427) ~[vmware-identity-platform.jar:?]
        at com.vmware.identity.interop.registry.LinuxRegistryAdapter.openKey(LinuxRegistryAdapter.java:77) ~[vmware-identity-platform.jar:?]
        at com.vmware.identity.interop.registry.LinuxRegistryAdapter.openRootKey(LinuxRegistryAdapter.java:88) ~[vmware-identity-platform.jar:?]
        at com.vmware.identity.idm.server.config.IdmServerConfig.<init>(IdmServerConfig.java:372) ~[vmware-identity-idm-server.jar:?]
        at com.vmware.identity.idm.server.config.IdmServerConfig.<clinit>(IdmServerConfig.java:145) ~[vmware-identity-idm-server.jar:?]
        at com.vmware.identity.idm.server.config.ConfigStoreFactory.<init>(ConfigStoreFactory.java:34) ~[vmware-identity-idm-server.jar:?]
        at com.vmware.identity.idm.server.IdentityManager.<init>(IdentityManager.java:401) ~[vmware-identity-idm-server.jar:?]
        at com.vmware.identity.idm.server.IdentityManager.getIdmInstance(IdentityManager.java:12878) ~[vmware-identity-idm-server.jar:?]
        at com.vmware.identity.idm.client.CasIdmClient.<init>(CasIdmClient.java:154) ~[vmware-identity-idm-client.jar:?]
        at com.vmware.identity.idm.client.CasIdmClient.<init>(CasIdmClient.java:141) ~[vmware-identity-idm-client.jar:?]
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_345]

Example Patchrunner.log:

Cause

Issue is caused by a currently under investigation issue connected to domain joined vCenters:

https://knowledge.broadcom.com/external/article?articleId=378362

Resolution

Revert to snapshot taken before the patching attempt, or if the vami has option to roll back from the failed patch this can also be attempted.

Check if the vCenter is domain joined:
/opt/likewise/bin/domainjoin-cli query
Then unjoin vCenter from the domain with following command:
/opt/likewise/bin/domainjoin-cli leave
Reboot the vCenter
Attempt the patch again.
If successful rejoin domain if it is a requirement.