The deployment of a Multi VCF environment (VCF 9.0.1) where the Fleet is shared across two instances involved the following steps:
The Fleet deployment for Instance 1 failed at the task "Import VCF Operations in Fleet Lifecycle" with an the following exception
com.vmware.vrealize.lcm.util.exception.AuthorizationFailedException: java.lang.RuntimeException: Error occurred while invoking API Task : [Failed to send task to Collector with id: 4]
at com.vmware.vrealize.lcm.util.VmspISUtils.getSessionToken(VmspISUtils.java:93)
at com.vmware.vrealize.lcm.util.VmspISUtils.getHeaders(VmspISUtils.java:72)
at com.vmware.vrealize.lcm.vmsp.plugin.tasks.CreateServiceAccountTask.execute(CreateServiceAccountTask.java:101)
at com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:76)
at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:48)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source) "
SDDC-Manager 9.1
In SDDC Manager 9.1, the process to "complete the fleet" involves deploying fleet management components and importing the existing Ops service. This import task necessitates a healthy and configured cloud proxy. However, a crucial health precheck for the cloud proxy is absent in this SDDC-M version. Consequently, the workflow may proceed despite an unhealthy cloud proxy, leading to a failure at a later stage.
Deploy new Cloud Proxy from VCF Operations UI. See Deploy Cloud Proxy as part of a VCF 9.1 Upgrade