Refer to the tips in this topic to troubleshoot TKG release content library errors.

No TKR Resources Found

A vSphere administrator has created a content library and synchronized it with supported TKG releases. You have assigned the content library to the vSphere Namespace where you are deploying TKG clusters. You are logged in to Supervisor and have switched context to the vSphere Namespace.

Running the following commands returns No resources found. 
kubectl get tanzukubernetesreleases
kubectl get tkr
To troubleshoot, run the following commands. 
kubectl get virtualmachineimages -A
kubectl get vmimage -o wide
Check to see if the content library exists and is registered with the namespace. 
kubectl get contentsources
 kubectl get contentsourcebindings -A

To resolve, log in to the vCenter Server Management interface. Navigate to Services, select the Content Library Service and click Restart.

If this does not resolve the issue, you may have to remove the content library from the namespace. To do this, create a new content library and add it to the namespace, removing the previous one.

Get Library Items Fails

When attempting to provision a TKG cluster, you are unable to pull items from a subscribed content library that is synchronized and associated with the vSphere Namespace.

The following error appears: 
Internal error occurred: get library items failed for.

If the subscribed content Library reaches storage capacity limits, you cannot provision TKG clusters. The content library is backed by attached storage. Over time, as more Kubernetes versions are released and OVA files are synchronized into the library, the storage might fill to capacity.

If you are automatically synchronizing TKRs, consider switching to manual synchronization and only store locally those TKR images you need. If you are already using on-demand synchronization, prune those images you no longer need from the library. Alternatively, you can migrate to a new content library.

TKR Cannot Be Found in the Local Content Library

Local content libraries can be used in internet-restricted environments.

When you create the local content library, you have the option of applying a Security Policy to the library. Even if the Tanzu Kubernetes release has been uploaded to the library, the release will not be available for use by TKG clusters if one of the following conditions exist.
  • The OVF package in the content library are not signed.
  • The OVF package is signed using an invalid certificate.
  • The OVF package is signed using a certificate not trusted by the vCenter Server where the Local Content Library is configured.

When you upload the OVA and VMDK files to the content library, make sure the certificate the manifest files are in the home directory from where you are uploading the file.