Some of these below mentioned symptoms can occur (if not all):
Workflow failure with following logs from domain manager service of SDDC manager. The domain manager logs can be found at (/var/log/vmware/vcf/domainmanager/domainmanager.log)
2022-11-21T17:11:28.525+0000 ERROR [vcf_dm,7ecdee40267a414a,ee56] [c.v.e.s.c.h.i.HostPreparationServiceImpl,dm-exec-17] Failed to configure disks on esxi.domain.com. Error: Error when executing 'Mark SSD disks as capacity on ESXi server esxi.domain.com' - exit code 1.
com.vmware.evo.sddc.common.util.command.CommandExecuterException: Error when executing 'Mark SSD disks as capacity on ESXi server esxi.domain.com' - exit code 1.
at com.vmware.evo.sddc.common.util.command.CommandResult.validateSuccess(CommandResult.java:139)
at com.vmware.evo.sddc.common.util.command.CommandResult.validateSuccess(CommandResult.java:111)
at com.vmware.evo.sddc.common.hostservices.impl.HostPreparationServiceImpl.configureDisks(HostPreparationServiceImpl.java:198) ....
Checking the output of vdq -vq from the logs:
2022-11-21T17:11:24.676+0000 DEBUG [vcf_dm,7ecdee40267a414a,ee56] [c.v.evo.sddc.common.util.SshUtil,dm-exec-17] The command [ vdq -q ] executed on host. Status: 0, Timed out: false
Output: [
{
"Name" : "eui.3643533052b026420025384500000002",
"VSANUUID" : "",
"State" : "Eligible for use by VSAN",
"Reason" : "None",
"IsSSD" : "1",
"IsCapacityFlash": "0",
"IsPDL" : "0",
"Size(MB)" : "1831420",
"FormatType" : "512e",
"IsVsanDirectDisk" : "0"
}, ...
This issue is fixed in the VCF 5.x release.
Workaround:
To workaround the issue, please follow the below mentioned steps:
Download the attached capacity-disk-tagging.tar.gz. Execute the below steps and then restart the failed workflow. These steps can be executed even before starting workflow so that the above failures will not be seen during execution of workflow.
tar xvf capacity-disk-tagging.tar.gz
pip-3 install paramiko
pip-3 install SCPClient
pip-3 install scp
python3 /tmp/capacity-disk-tagging/capacityflashtaghost.py