VCF Installer workflow task fails at VCF Automation deployment with 404 error

Products

• VMware SDDC Manager
• VCF Automation

Issue/Introduction

• The VCF Installer workflow fails during the VCF Automation (VCF-A) deployment stage.
• In some use-cases, VCF-A virtual machine (VM) has been deleted from the inventory.
• The following failed task is observed in the VCF Installer UI:

  Retrieve the status of VCF Automation Deployment request - Failed - MM/DD/YY, HH:MM
  Unable to get request status for request <Request_ID> Reference Token: ######

• domainmanager.log:

  YYYY-MM-DDTHH:MM:SS.###+0000 DEBUG [vcf_dm,<Task_ID>,####] [c.v.e.s.r.c.LoggingHttpRequestInterceptor,dm-exec-##]  Request URI: https://<VCF_FLEET_MANAGER_FQDN>/lcm/request/api/v2/requests/<Request_ID>
  >Request method: GET
  >Request body:
  >Response code: 404 NOT_FOUND

Environment

• VCF Installer 9.0.x
• VCF SDDC Manager 9.0.x
• VCF Fleet Management 9.0.x
• VCF Automation 9.0.x

Cause

The VCF Installer task requires the VCF-A virtual machine to be active and reachable to progress the workflow. Because the VM was deleted, the installer receives a 404 NOT_FOUND response when attempting to query or interact with the appliance, causing the workflow to stall.

Resolution

To workaround this issue, the failed VCF-A task(s) must be skipped in the VCF Installer database to allow the main installer workflow to complete. The VCF-A component can then be deployed as a "Day N" activity. via this documentation VCF Management Components - Deploy Use Case

 

Should you want to get past / skip the failed task, please note this Knowledge Article ID (425177) in the problem description and contact Broadcom Support.