"VMware Directory Service schema update failed" while upgrading from vCenter Server 7.0 to 7.0 Update1
Article ID: 318148
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
- Upgrade fails during the validation stage from 7.0 to 7.0 Update 1 with error "VMware Directory Service schema update failed" in Pre-Update Check Results.
- The error will reveal a pre-check failure:
- In the PatchRunner.log file, you see similar to:
Traceback (most recent call last):
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor.py", line 74, in executeHook
executionResult = systemExtension(args)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/libs/sdk/extensions.py", line 106, in __call__
result = self.extension(*args)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/libs/sdk/extensions.py", line 123, in _func
return func(*args)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/payload/components-script/vmdir/__init__.py", line 303, in patch
_postInstallScripts(ctx)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/payload/components-script/vmdir/__init__.py", line 124, in _postInstallScripts
update_schema()
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/payload/components-script/vmdir/__init__.py", line 194, in update_schema
raise InternalError("Vmware Directory Service schema update failed" )
patch_errors.InternalError: Vmware Directory Service schema update failed
YYYY-MM-DDTHH:MM:SS ERROR vmware_b2b.patching.phases.patcher Patch hook Patch got ComponentWrapperError.
Traceback (most recent call last):
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/phases/patcher.py", line 199, in patch
_patchComponents(ctx, userData, statusAggregator.reportingQueue)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/phases/patcher.py", line 86, in _patchComponents
executeComponentHook(Hook.Patch, ctx, c, userData, reportingQueue)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/execution_facade.py", line 98, in executeComponentHook
reportQueue, identifier, expectedResultType)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/execution_facade.py", line 53, in executeHook
result = executor.executeHook(scriptFile, hook, args, reportQueue, reportIdentifier)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor_process.py", line 119, in executeHook
raise ex
patch_errors.ComponentError
YYYY-MM-DDTHH:MM:SS WARNING root stopping status aggregation...
YYYY-MM-DDTHH:MM:SS ERROR __main__ Patch vCSA failed
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor.py", line 74, in executeHook
executionResult = systemExtension(args)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/libs/sdk/extensions.py", line 106, in __call__
result = self.extension(*args)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/libs/sdk/extensions.py", line 123, in _func
return func(*args)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/payload/components-script/vmdir/__init__.py", line 303, in patch
_postInstallScripts(ctx)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/payload/components-script/vmdir/__init__.py", line 124, in _postInstallScripts
update_schema()
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/payload/components-script/vmdir/__init__.py", line 194, in update_schema
raise InternalError("Vmware Directory Service schema update failed" )
patch_errors.InternalError: Vmware Directory Service schema update failed
YYYY-MM-DDTHH:MM:SS ERROR vmware_b2b.patching.phases.patcher Patch hook Patch got ComponentWrapperError.
Traceback (most recent call last):
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/phases/patcher.py", line 199, in patch
_patchComponents(ctx, userData, statusAggregator.reportingQueue)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/phases/patcher.py", line 86, in _patchComponents
executeComponentHook(Hook.Patch, ctx, c, userData, reportingQueue)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/execution_facade.py", line 98, in executeComponentHook
reportQueue, identifier, expectedResultType)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/execution_facade.py", line 53, in executeHook
result = executor.executeHook(scriptFile, hook, args, reportQueue, reportIdentifier)
File "/storage/seat/software-updatedz69uquh/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor_process.py", line 119, in executeHook
raise ex
patch_errors.ComponentError
YYYY-MM-DDTHH:MM:SS WARNING root stopping status aggregation...
YYYY-MM-DDTHH:MM:SS ERROR __main__ Patch vCSA failed
- You will see similar error in /var/log/vmware/vmdird/vmdird-syslog.log file,
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: UpdateToDate Vector: (417fba43-4d2b-486c-bc6c-9a818fbf8fb0:51174,eb037001-9100-11ea-a7e6-005056ab58c4:45190,dfa9e341-90fd-11ea-992d-005056a09017:49693,)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: Server ID (3), InvocationID (8caf64a3-c70d-4995-9167-f17e9af5efef)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: Domain Functional Level (4)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: VmDirKrbInit, REALM (VSPHERE.LOCAL)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: ACL MODE: Legacy
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: >>> Schema patch starts <<<
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: New schema instance (0x2a9d1b0)
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: CoreLogicModifyEntry failed, DN = cn=aggregate,cn=schemacontext, Error (9700), Message (BEEntryModify, (9700)((MDB_BAD_VALSIZE: Too big key/data, key is empty, or wrong DUPFIXED size)(objectClasses)))
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: InternalModifyEntry: VdirExecutePostModifyCommitPlugins - code(9700)
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: VmDirUpdateSubSchemaSubEntry failed, error (9700)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: VmDirPatchLocalSubSchemaSubEntry did not succeed (9700)
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: VmDirSchemaPatchViaFile failed, error (9700)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: Server ID (3), InvocationID (8caf64a3-c70d-4995-9167-f17e9af5efef)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: Domain Functional Level (4)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: VmDirKrbInit, REALM (VSPHERE.LOCAL)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: ACL MODE: Legacy
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: >>> Schema patch starts <<<
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: New schema instance (0x2a9d1b0)
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: CoreLogicModifyEntry failed, DN = cn=aggregate,cn=schemacontext, Error (9700), Message (BEEntryModify, (9700)((MDB_BAD_VALSIZE: Too big key/data, key is empty, or wrong DUPFIXED size)(objectClasses)))
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: InternalModifyEntry: VdirExecutePostModifyCommitPlugins - code(9700)
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: VmDirUpdateSubSchemaSubEntry failed, error (9700)
YYYY-MM-DDTHH:MM:SS info vmdird t@139837142824768: VmDirPatchLocalSubSchemaSubEntry did not succeed (9700)
YYYY-MM-DDTHH:MM:SS err vmdird t@139837142824768: VmDirSchemaPatchViaFile failed, error (9700)
Environment
VMware vCenter Server 7.0.x
Cause
This issue occurs when VMDIR Legacy schema patching fails while updating vCenter Server from 7.0 to 7.0 Update 1 if the Domain Functional Level of VMDIR is 4
The issue is typically seen in environments where vCenter has been migrated from 6.5 to 6.7 to 7.0 and then updated to 7.0 U1
The issue is typically seen in environments where vCenter has been migrated from 6.5 to 6.7 to 7.0 and then updated to 7.0 U1
Resolution
This issue is fixed in vCenter Server 7.0 Update 1 C, available at https://support.broadcom.com/#search
Workaround:
No workaround available
Please subscribe to the KB to receive notifications on this issue.
Workaround:
No workaround available
Please subscribe to the KB to receive notifications on this issue.
Feedback
Yes
No
Powered by
