53: server misbehaving

[tiansiyuan]

What steps did you take:
kubectl get packagerepository kubeflow-carvel-repo -o=jsonpath={.status.usefulErrorMessage}

What happened:
vendir: Error: Syncing directory '0':
Syncing directory '.' with imgpkgBundle contents:
Fetching image:
Error while preparing a transport to talk with the registry:
Unable to create round tripper:
Get "https://projects.registry.vmware.com/v2/": dial tcp: lookup projects.registry.vmware.com on 10.152.183.10:53: server misbehaving

What did you expect:
[A description of what was expected and the yaml that should have been generated]

Anything else you would like to add:
[Additional information that will assist in solving the issue.]

[praveenrewar]

Hey @tiansiyuan! Could you share more information on what was your expected behaviour and how was it different from the output that you got.
(Based on the output that you shared it seems like you are not able to connect to the registry from where you are trying to fetch config.)

[tiansiyuan]

Hi @praveenrewar This was diagnosis I made after searching for solution my issue.

I could not add carvel package repository. The output is similar:

$ kctrl -n carvel-kubeflow-namespace package repository add  --repository kubeflow-carvel-repo  --url [projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1](http://projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1)
Target cluster 'https://10.117.4.12:16443/' (nodes: ai-poweredge-t620)
Waiting for package repository to be updated
4:18:11PM: Waiting for package repository reconciliation for 'kubeflow-carvel-repo'
4:24:31PM: Fetch failed
	  | vendir: Error: Syncing directory '0':
	  |  Syncing directory '.' with imgpkgBundle contents:
	  |   Fetching image:
	  |    Error while preparing a transport to talk with the registry:
	  |     Unable to create round tripper:
	  |      Get "https://projects.registry.vmware.com/v2/": dial tcp: lookup [projects.registry.vmware.com](http://projects.registry.vmware.com/) on 10.152.183.10:53: server misbehaving
	  |
	  | Fetching resources: Error (see .status.usefulErrorMessage for details)
kctrl: Error: Reconciling repository:
 Fetch failed

I expected I could add it and install the packages as next step.

The whole procedure is described at https://github.com/vmware/vSphere-machine-learning-extension/blob/main/docs/install/tkgs.rst

[praveenrewar]

@tiansiyuan The url should just be projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1 and not [projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1](http://projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1).

Do you have access to projects.registry.vmware.com? Are you able to pull from the registry from another pod?

[renuy]

We have transferred to kapp-controller repo from carvel repo.

[tiansiyuan]

@tiansiyuan The url should just be projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1 and not [projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1](http://projects.registry.vmware.com/kubeflow/kubeflow-carvel-repo:1.6.1).

Do you have access to projects.registry.vmware.com? Are you able to pull from the registry from another pod?

I do have access to projects.registry.vmware.com.

"https://" was added by github while editing the comment.

[tiansiyuan]

We have transferred to kapp-controller repo from carvel repo.

@renuy Thank you. Could you tell me the issue number?

[praveenrewar]

I do have access to projects.registry.vmware.com.

Are you able to pull from the registry from another pod in the same namespace?

Could you tell me the issue number?

We have transferred the issue in the same org (from one repo to another, as the carvel repo is used for docs), the number that you see on the top (1437) is the issue number.

[tiansiyuan]

I do have access to projects.registry.vmware.com.

Are you able to pull from the registry from another pod in the same namespace?

I don't quite understand how to try this. Could you provide more info?

Thanks!

Could you tell me the issue number?

We have transferred the issue in the same org (from one repo to another, as the carvel repo is used for docs), the number that you see on the top (1437) is the issue number.

[praveenrewar]

@tiansiyuan You can ssh into some other pod in the same namespace and see if you are able to access the registry there.