An error occurred in task "Prepare input for adding Cloud Proxy to existing VCF Operations deployment". See Tasks panel to learn more.
Subtask: Prepare input for adding Cloud Proxy to existing VCF Operations deployment. Input preparation for adding VCF Cloud Proxy node to existing VCF Operations has failed Reference Token: ####
Milestone: Join the existing operations appliance
Description: Prepare input for adding Cloud Proxy to existing VCF Operations deployment
Status: Failed
https://<vcf_operations_fqdn>/casa/node/status returns an address of vcf_operations_IP, where an address of <vcf_operations_fqdn> is expectedYYYY-MM-DDThh:mm:ss.sss+0000 DEBUG [vcf_dm,####,####] [c.v.v.v.s.f.FleetLcmApiRetryWrapper,dm-exec-####] Non-retryable error encountered for operation 'Fleet LCM getComponents for <vcf_operations_fqdn>': Failed to find component of type OPS with FQDN <vcf_operations_fqdn>
YYYY-MM-DDThh:mm:ss.sss+0000 ERROR [vcf_dm,####,####] [c.v.e.s.c.util.RetriableCallable,dm-exec-####] Non retriable exception while retrying operationcom.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to find component of type OPS with FQDN <vcf_operations_fqdn>
YYYY-MM-DDThh:mm:ss.sss+0000 ERROR [vcf_dm,####,####] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-####] [####] FLEET_ADD_CLOUD_PROXY_NODE_INPUT_PREPARATION_FAILED Input preparation for adding VCF Cloud Proxy node to existing VCF Operations has failedcom.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Input preparation for adding VCF Cloud Proxy node to existing VCF Operations has failed
VCF 9.1.0.0100
The VCF Operations master node is registered in the SDDC Manager lifecycle databases (fleetlcm and sddclcm) using its IP address instead of its fqdn in the hostname field.
The VCF Installer fails to locate the component because it performs lookups based on the fqdn.
Querying GET /casa/node/status on the VCF Operations node incorrectly reports an IP address instead of the expected fqdn (in a browser, open URL - https://<vcf_operations_fqdn>/casa/node/status).
Please open a case with Broadcom Technical Support and reference this article to have the issue resolved.