kubevirt/hyperconverged-cluster-operator

ImagePullBackOff for hco-operator and hco-webhook

Closed this issue · 4 comments

manas-suleman commented

What happened:
ImagePullBackOff error for hco-operator and hco-webhook. Both pods fail to pull the required image.

What you expected to happen:
hco-operator and hco-webhook pull the image successfully, create the container and pod status changes to Running.

How to reproduce it (as minimally and precisely as possible):
I'm using the following documentation: https://docs.okd.io/4.15/virt/install/installing-virt.html
These are the steps I followed:

  1. Install OKD4.15 bare-metal with 3 masters.
  2. On OperatorHub, Install "KubeVirt HyperConverged Cluster Operator" with the following options,
    • Update channel: Stable
    • Version: 1.10.0
    • Installation Mode: All namespaces on the cluster (default)
    • Installed Namespace: Operator recommended Namespace: kubevirt-hyperconverged
    • Update approval: Automatic
  3. Check pod creation. All pods go into "Running" state except hco-operator and hco-webhook.

Additional context:
Add any other context about the problem here.

Environment:

  • KubeVirt version (use virtctl version): N/A
  • Kubernetes version (use kubectl version): v1.28.2-3598+6e2789bbd58938-dirty
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: bare-metal
  • OS (e.g. from /etc/os-release): Fedora CoreOS
  • Kernel (e.g. uname -a): 6.7.4-200.fc39.x86_64
  • Install tools: N/A
  • Others: N/A
orenc1 commented

Thanks for reporting, @manas-suleman !
It looks like the stable channel in the community operators catalog is pointing to an obsolete version, v1.10.0.
We'll fix it. In the meanwhile you can use channel 1.11.0 or 1.10.7 for the desired version.
cc: @nunnatsa

manas-suleman commented

Thanks for the update @orenc1. I can confirm successful installation using 1.10.7 version. Cheers for that.

nunnatsa commented

As far as I can see, the catalog.json file within the catalog-source pod, contains both the 1.10.7 and the stable channel. In the new versions, after we fixed the index image issues we had, we no longer create "stable" channel. I guess that that why the new channel was added instead of replacing the old stable channel.

However, the new fixed channel is also the default channel. When installing this from OKD UI, the rigth channel is set by default.

Still, we need to find out how to remove the old channel. @orenc1 - any idea?