ESX Upgrade VUM Stage Scan Host task Failed
The upgrade has VIBs that are missing dependencies. Remove the VIBs or use Image Builder to create a custom upgrade ISO image that contains the missing dependencies, and try to upgrade again
VMware Cloud Foundation
When ESXi Host is installed using Custom Image there are a few OEM Bundle/vibs contained in it which are not present in Vanilla Image leading to Patch/Upgrade failure
mkdir /nfs/vmware/vcf/nfs-mount/esx-upgrade-partner-binaries
chmod -R 775 /nfs/vmware/vcf/nfs-mount/esx-upgrade-partner-binaries/
chown -R vcf_lcm:vcf /nfs/vmware/vcf/nfs-mount/esx-upgrade-partner-binaries/
{
"esxCustomImageSpecList": [{
"bundleId": "bundle ID of the ESXi bundle available in Bundle Management Section of SDDC Manager",
"targetEsxVersion": "ESXi version for the target VMware Cloud Foundation version",
"useVcfBundle": false,
"domainId": "########-####-####-########",
"clusterId": "########-####-####-########",
"customIsoAbsolutePath": "Path_to_image_of_custom_ISO"
}]
}
where
|
Parameter
|
Description and Example Value
|
|---|---|
|
bundleId
|
ID of the Vanilla ESXi upgrade bundle downloaded through Bundle Management of SDDC. You can retrieve the bundle ID by navigating to the
Lifecycle Management > Bundle Management page and clicking View Details to view the bundle ID.
For example,
8c0de63d-b522-4db8-be6c-f1e0ab7ef554
.
Note, ID for Custom Image uploaded will not be shown in Bundle Managment hence Bundle ID of ESXi upgrade bundle downloaded through Bundle Management of SDDC is required to be used here
|
|
targetEsxVersion
|
Version of the ESXi bundle you downloaded. You can retrieve the target ESXi version by navigating to the
Lifecycle Management > Bundle Management page and clicking View Details to view the "Update to Version".
|
|
useVcfBundle
|
Specifies whether the VMware Cloud Foundation ESXi bundle is to be used for the upgrade.
If you want to upgrade with a custom image, ensure that this is set to false.
|
|
domainId
(optional, VCF 4.4.1.1 and later only) |
ID of the specific workload domain where the custom image needs to be applied.
Use the VMware Cloud Foundation API (GET /v1/domains) to get the IDs for your workload domains.
|
|
clusterId
(optional, VCF 4.4.1.1 and later only) |
ID of the specific cluster within a workload domain to apply the custom image. If you do not specify a
clusterId, the custom image will be applied to all clusters in the workload domain. Use the VMware Cloud Foundation API (GET /v1/clusters) to get the IDs for your clusters.
|
|
customIsoAbsolutePath
|
Path to the custom image file on the SDDC Manager appliance For example, /nfs/vmware/vcf/nfs-mount/esx-upgrade-partner-binaries/VMware-VMvisor-Installer-7.0.0.update01-17325551.x86_64-DellEMC_Customized-A01.iso
Note, Please make sure the path is correct else the upgrade will proceed with the VMware Cloud Foundation stock image bundle and replace the custom VIBs in your environment with the stock VIB's or the activity may fail with same vib dependency error. |
{
"esxCustomImageSpecList": [{
"bundleId": "8c0de63d-b522-4db8-be6c-f1e0ab7ef554",
"targetEsxVersion": "8.0.1-########",
"useVcfBundle": false,
"customIsoAbsolutePath":
"/nfs/vmware/vcf/nfs-mount/esx-upgrade-partner-binaries/VMware-VMvisor-Installer-8.0.0.update01-########.x86_64-DellEMC_Customized-A01.iso"
}]
}
For Example if you have 2 Cluster one is Dell and other one is HPE Cluster then the esx-custom-image-upgrade-spec.json should look like:
{
"esxCustomImageSpecList": [
{
"bundleId": "aa7b16b1-########-9ced-########",
"targetEsxVersion": "8.0.2-########",
"useVcfBundle": false,
"domainId": "########-####-####-########",
"clusterId": "########-####-####-########",
"customIsoAbsolutePath": "/nfs/vmware/vcf/nfs-mount/esx-upgrade-partner-binaries/VMware-ESXi-8.0.2-23305546-DELL.iso"
},
{
"bundleId": "aa7b16b1-########-44b7-9cfd-########",
"targetEsxVersion": "7.0.1-########",
"useVcfBundle": false,
"domainId": "########-####-####-########",
"clusterId": "########-####-####-########",
"customIsoAbsolutePath": "/nfs/vmware/vcf/nfs-mount/esx-upgrade-partner-binaries/VMware-ESXi-7.0.2-17867351-HP.iso"
}
]
}
chmod -R 775 /nfs/vmware/vcf/nfs-mount/esx-custom-image-upgrade-spec.json
chown -R vcf_lcm:vcf /nfs/vmware/vcf/nfs-mount/esx-custom-image-upgrade-spec.json
lcm.esx.upgrade.custom.image.spec=/nfs/vmware/vcf/nfs-mount/esx-custom-image-upgrade-spec.json
systemctl restart lcm
Please reach out to Broadcom Support in case or any question or clarification needed while following the KB