VCF Installer vCenter deployment fails: Host seeding or VIB extraction error
search cancel

VCF Installer vCenter deployment fails: Host seeding or VIB extraction error

book

Article ID: 431474

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • VMware Cloud Foundation installer fails during vCenter server installation. The installation completes and VAMI page shall be accessible, however, the installation rolls back, deleting the vCenter server instance. The VCF installer shows the error message similar to:

 

 

  • Domain Manager logs reports about the vCenter installation failure along with Token ID, redirecting further analysis to be performed from ci-installer-<date>

 

/var/log/vmware/vcf/domainmanager/domainmanager.log

 

YYYY-MM-DDTHH:MIN:SEC ERROR [vcf_dm,######,0213] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-24]  [Token ID] VCF_VSPHERE_VCENTER_INSTALLATION_FAILED vCenter installation failed. Check logs under /var/log/vmware/vcf/domainmanager/ci-installer-YYYYMMDD## for more details.
com.vmware.vcf.common.util.VsphereRuntimeException: vCenter installation failed. Check logs under /var/log/vmware/vcf/domainmanager/ci-installer-YYYYMMDD## for more details.
        at com.vmware.vcf.common.util.VsphereContractActionUtils.deployVC(VsphereContractActionUtils.java:281)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 

  • The ci-installer-<date> reported vCenter server installation failure during cluster creation. It further states about an error occurrence while extracting image info on the host.

 

/var/log/vmware/vcf/domainmanager/ci-installer-YYYYMMDD##

 


YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - INFO -  [SUCCEEDED] Successfully executed Task 'Running Datacenter Creation: Creating the new datacenter for vSphere vLCM managed cluster.' in TaskFlow 'ci-conf-######' at HH:MIN:SEC
YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - INFO -  [START] Start executing Task: Creating vSphere vLCM managed cluster. at HH:MIN:SEC
YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - DEBUG - Proceed with certificate check...
YYYY-MM-DDTHH:MIN:SEC vCSACliInstallLogger - DEBUG - Successfully found the target VCSA 'vCenter-name on esxi 'example.fqdn.com'
YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - DEBUG - Found FQDN of target appliance: vCenter.fqdn
YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - INFO - Enabling vLCM Cluster creation task on vCenter.fqdn
YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - INFO - Connecting to esx host: example.fqdn.com
YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - INFO - ============== [FAILED] Task: Running vSphere vLCM: Creating vSphere vLCM managed cluster. execution failed at HH:MIN:SEC ==============
YYYY-MM-DDTHH:MIN:SEC - vCSACliInstallLogger - DEBUG - Task 'Running vSphere vLCM: Creating vSphere vLCM managed cluster.' execution failed because [Host seeding failed:(vmodl.MethodFault) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   msg = 'MethodFault.summary',
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [
      (vmodl.LocalizableMessage) {
         dynamicType = <unset>,
         dynamicProperty = (vmodl.DynamicProperty) [],
         key = 'com.vmware.vcint.error_from_vlcm',
         arg = (vmodl.KeyAnyValue) [
            (vmodl.KeyAnyValue) {
               dynamicType = <unset>,
               dynamicProperty = (vmodl.DynamicProperty) [],
               key = 'vlcm_error',
               value = 'Error:\n   com.vmware.vapi.std.errors.error\nMessages:\n com.vmware.vcIntegrity.lifecycle.EsxImage.SoftwareInfoExtractError<An error occurred while extracting image info on the host.>\n   com.vmware.vcIntegrity.lifecycle.ExtractDepotTask.HostExtractDepotFailed<Extraction of image from host 'example.fqdn.com' failed.>\n' message = "An internal error occurred: 'Error:\n   com.vmware.vapi.std.errors.error\nMessages:\n   com.vmware.vcIntegrity.lifecycle.EsxImage.SoftwareInfoExtractError<An error occurred while extracting image info on the host. > com.vmware.vcIntegrity.lifecycle.ExtractDepotTask.HostExtractDepotFailed<Extraction of image from host 'example.fqdn.com' failed.

 

  • ESX Lifecycle logs from the above referenced ESX host, states about vib being marked as Orphan.

 

/var/log/lifecycle.log found in ESX host:

 

YYYY-MM-DDTHH:MIN:SEC Er(11) lifecycle[2138933]: HostSeeding:736 BaseImg Comps are removed: {'name of the vib'}
YYYY-MM-DDTHH:MIN:SEC Db(15) lifecycle[2138933]: HostSeeding:766 List of Orphan Vibs: {'vib': 'version'}
YYYY-MM-DDTHH:MIN:SEC Er(11) lifecycle[2138933]: HostSeeding:919 Software info extract errors: The following Components have been removed on the host: <name of the conflicting vib>

 

Environment

VCF 9.x

Cause

Conflicting VIBs of current version with that of Image Profile. This can be due to incompatible or legacy version of the vib running on ESX host. 

Resolution

To address the issue, it involves 3 steps; validate hardware compatibility, verify the affected vib, and update the affected vib.

  1. Check the compatibility of the physical server by following the steps mentioned in Checking Host Compatibility Before Upgrade Using the Broadcom Compatibility Guide
  2. If the affected vib is associated with Storage/Networking, follow the steps mentioned in Determining Network/Storage firmware and driver version in ESXi
  3. Update a Host with Individual VIBs by following the instructions mentioned in Broadcom TechDocs
Powered by Wolken Software