Operational Defect Database
BugZero updated this defect 46 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 94698
TKC cluster creation fails with "deploy from content library failed for image" error
Last update date:
4/3/2024
Affected products:
vSphere
Affected releases:
7.0
Fixed releases:
No fixed releases provided.
Description:
Symptoms
TKGs TKC cluster creation fails with the following errors: deploy from content library failed for image "ob-18592554-photon-3-k8s-v1.21.2---vmware.1-tkg.1.ee25d55": deploy error: The operation failed due to An error occurred during host configuration.error creating client and cache for remote cluster: error creating dynamic rest mapper for remote cluster "test/tkg-test4": Get "https://10.250.32.3:6443/api?timeout=10s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)Waiting for control plane to pass preflight checks to continue reconciliation: [machine tkg-test4-control-plane-m2f5l does not have APIServerPodHealthy condition, machine tkg-test4-control-plane-m2f5l does not have ControllerManagerPodHealthy condition, machine tkg-test4-control-plane-m2f5l does not have SchedulerPodHealthy condition, machine tkg-test4-control-plane-m2f5l does not have EtcdPodHealthy condition, machine tkg-test4-control-plane-m2f5l does not have EtcdMemberHealthy condition]
Purpose
This article is a reference to https://community.pivotal.io/s/question/0D58X0000BwWhtuSQC/error-when-creating-taznu-kubernetes-cluster?language=en_US where steps to recover a failed TKC cluster deployment due to errors with the Content Library are provided.
Cause
Possible causes include Content Library connection issues which make it impossible for WCP to fetch the necessary TKC images.
Impact / Risks
The Resolution steps do not have any known negative impact on the deployment.
Resolution
Below resolution is a copy-paste from https://community.pivotal.io/s/question/0D58X0000BwWhtuSQC/error-when-creating-taznu-kubernetes-cluster?language=en_US If you have more than one Content library you can skip reading to Part 2. Part 1 We need to create new content library so from vSphere menu choose: Content Libraries then click Create and make new one in the same workload domain as Tanzu is. After you done this add any ovf or any iso image with whatever to it. Part 2 Use menu and and go to: Workload Management Find you Supervisor Cluster tab an click on it or Choose you cluster from main menu Use Configure tab Click EDIT and choose you newly created Content Library or any other if you have more than one and confirm by OK button. After that we need to wait to vSphere Fetch this Content Library Don't worry about Information. After vSphere end fetching items from new Content Library we need to repeat the steps from moment when we change it to go back to our old CL. The vSphere do the same thing as it do with new one but also refresh it if you have automatic content download enabled and choose to download it as soon as possible. When it finish to fetch libraries we can easily create TKC clusters.
Related Information
Original article: https://community.pivotal.io/s/question/0D58X0000BwWhtuSQC/error-when-creating-taznu-kubernetes-cluster?language=en_US
