Missing Collectors in VCF Operations After Deploying VCF Network Collector via Fleet Services API

Products

• VCF Operations

Issue/Introduction

• Using the API to deploy a new VCF Network Collector via a PATCH request to Fleet Services (https://########/fleet-lcm/v1/components/########) that includes the fqdn field, the collector is registered successfully within vRNI, however, VCF Operations incorrectly displays only the new collector.
• The VMs are running correctly and function without issue inside vRNI.

Environment

VCF Operations 9.1

Cause

A bug in the Fleet LCM post-success deployment verification code causes a key-format mismatch between the expected hostname (FQDN) and the IP address reported by SBS for collector node identity when the FQDN field is passed for each collector node in the payload.

Resolution

1. Send the API configuration payload without the FQDN fields defined for the existing nodes to allow the task for the existing collectors to complete successfully.
2. Once the initial configuration task finishes, send the payload with a single collector to finalize the deployment.