# Workload cluster failing logs

Tanzu Version : v0.11.2
OS : Linux
Provider: CAPD

Logs:

tanzu cluster create work.test --plan dev
Validating configuration...
I0322 10:45:56.797762  913853 request.go:665] Waited for 1.176582306s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.3:6443/apis/coordination.k8s.io/v1?timeout=32s
I0322 10:46:06.996924  913853 request.go:665] Waited for 11.375001234s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.3:6443/apis/controlplane.antrea.tanzu.vmware.com/v1beta1?timeout=32s
Warning: Pinniped configuration not found. Skipping pinniped configuration in workload cluster. Please refer to the documentation to check if you can configure pinniped on workload cluster manually
I0322 10:46:33.710981  913853 request.go:665] Waited for 1.028387674s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.3:6443/apis/acme.cert-manager.io/v1?timeout=30s
I0322 10:46:43.741471  913853 request.go:665] Waited for 2.028825555s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.3:6443/apis/cert-manager.io/v1?timeout=30s
Creating workload cluster 'work.test'...
Error: unable to create cluster: unable to apply cluster configuration: kubectl apply failed, output: cluster.cluster.x-k8s.io/work.test unchanged
kubeadmcontrolplane.controlplane.cluster.x-k8s.io/work.test-control-plane configured
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/work.test-md-0 unchanged
machinedeployment.cluster.x-k8s.io/work.test-md-0 unchanged
secret/work.test-antrea-addon configured
secret/work.test-kapp-controller-addon configured
secret/work.test-tkg-metadata-namespace-role configured
secret/work.test-tkg-metadata-configmap configured
secret/work.test-tkg-metadata-bom-configmap configured
clusterresourceset.addons.cluster.x-k8s.io/work.test-tkg-metadata unchanged
secret/work.test-metrics-server-addon configured
clusterresourceset.addons.cluster.x-k8s.io/work.test-core-package-repository unchanged
secret/work.test-core-package-repository-crs configured
secret/work.test-secretgen-controller-addon configured
machinehealthcheck.cluster.x-k8s.io/work.test configured
machinehealthcheck.cluster.x-k8s.io/work.test-control-plane configured
clusterresourceset.addons.cluster.x-k8s.io/work.test-capabilities unchanged
secret/work.test-capabilities configured
secret/work.test-config-values configured
Error from server (InternalError): error when creating "/tmp/kubeapply-1099164329": Internal error occurred: failed calling webhook "default.dockercluster.infrastructure.cluster.x-k8s.io": failed to call webhook: Post "https://capd-webhook-service.capd-system.svc:443/mutate-infrastructure-cluster-x-k8s-io-v1beta1-dockercluster?timeout=10s": context deadline exceeded
Error from server (InternalError): error when creating "/tmp/kubeapply-1099164329": Internal error occurred: failed calling webhook "validation.dockermachinetemplate.infrastructure.cluster.x-k8s.io": Post "https://capd-webhook-service.capd-system.svc:443/validate-infrastructure-cluster-x-k8s-io-v1beta1-dockermachinetemplate?timeout=10s": context deadline exceeded
Error from server (InternalError): error when creating "/tmp/kubeapply-1099164329": Internal error occurred: failed calling webhook "validation.dockermachinetemplate.infrastructure.cluster.x-k8s.io": Post "https://capd-webhook-service.capd-system.svc:443/validate-infrastructure-cluster-x-k8s-io-v1beta1-dockermachinetemplate?timeout=10s": context deadline exceeded
: exit status 1
Usage:
  tanzu cluster create CLUSTER_NAME [flags]

Flags:
  -d, --dry-run       Does not create cluster, but show the deployment YAML instead
  -f, --file string   Configuration file from which to create a cluster
  -h, --help          help for create
      --tkr string    TanzuKubernetesRelease(TKr) to be used for creating the workload cluster. If TKr name prefix is provided, the latest compatible TKr matching the TKr name prefix would be used

Global Flags:
      --log-file string   Log file path
  -v, --verbose int32     Number for the log level verbosity(0-9)

Error: exit status 1

✖  exit status 1 

# Harbor test got strucked while installing contour

Countour is installing fine while testing grafana but with harbor e2e-test it is failing with timout issue

Tanzu Version : v0.11.2
OS : Linux
Provider: CAPD
Logs:

+ tanzu package install contour --poll-interval 5s --poll-timeout 10m --namespace default --package-name contour.community.tanzu.vmware.com --version 1.20.1 --values-file fixtures/contour.yaml










Please consider using 'tanzu package installed update' to update the installed package with correct settings
Error: timed out waiting for the condition
Error: exit status 1

Failure [629.833 seconds]
[BeforeSuite] BeforeSuite 
/home/ubuntu/community-edition/addons/packages/harbor/2.3.3/test/e2e/harbor_suite_test.go:83

  Unexpected error:
      <*errors.errorString | 0xc0002241e0>: {
          s: "\n\n\n\n\n\n\n\n\n\nPlease consider using 'tanzu package installed update' to update the installed package with correct settings\nError: timed out waiting for the condition\nError: exit status 1\n\nexit status: 1",
      }
      
      
      
      
      
      
      
      
      
      
      Please consider using 'tanzu package installed update' to update the installed package with correct settings
      Error: timed out waiting for the condition
      Error: exit status 1
      
      exit status: 1
  occurred

  /home/ubuntu/community-edition/addons/packages/harbor/2.3.3/test/e2e/harbor_suite_test.go:291