Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capi-provider image can't be pulled off #5354

Open
youssefazrak opened this issue Jan 8, 2025 · 0 comments
Open

Capi-provider image can't be pulled off #5354

youssefazrak opened this issue Jan 8, 2025 · 0 comments

Comments

@youssefazrak
Copy link

Hi team,

I'm going through the documentation and installing an HCP cluster.
I'm following the documentation (see this link, prerequisite section), and building the binaries as it should be. Hypershift is installed but when creating an HCP cluster (whether I use hcp or hypershift cli), the capi-provider image is in ImagePullBackOff.

  Warning  Failed          12m (x6 over 14m)    kubelet            Error: ImagePullBackOff
  Normal   Pulling         12m (x4 over 14m)    kubelet            Pulling image "registry.ci.openshift.org/ocp/4.18:cluster-api-provider-kubevirt"
  Warning  Failed          12m (x4 over 14m)    kubelet            Failed to pull image "registry.ci.openshift.org/ocp/4.18:cluster-api-provider-kubevirt": reading manifest cluster-api-provider-kubevirt in registry.ci.openshift.org/ocp/4.18: authentication required
  Warning  Failed          12m (x4 over 14m)    kubelet            Error: ErrImagePull
  Normal   BackOff         4m1s (x44 over 14m)  kubelet            Back-off pulling image "registry.ci.openshift.org/ocp/4.18:cluster-api-provider-kubevirt"

What surprises me is the authentication requirement. I should be authenticated as the cluster has been created with this command:
./hypershift create cluster kubevirt --name hostedtest1 --network-type Other --node-pool-replicas=2 --base-domain test.local --pull-secret ~/pullsecret --generate-ssh --release-image quay.io/openshift-release-dev/ocp-release:4.16.26-multi --arch amd64 --vm-node-selector node.kubernetes.io/instance-type=m5.metal

My pull secret is the same one I use to build my OCP clusters (or ROSA clusters).

I've tried with multiple different versions, with no success.

Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant