Closed manas-suleman closed 5 months ago
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
Thanks for the update @orenc1. I can confirm successful installation using 1.10.7 version. Cheers for that.
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?
HCO v1.11.1
is now the head of the stable channel as for: https://operatorhub.io/operator/community-kubevirt-hyperconverged/stable/kubevirt-hyperconverged-operator.v1.11.1
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:
Additional context: Add any other context about the problem here.
Environment:
virtctl version
): N/Akubectl version
): v1.28.2-3598+6e2789bbd58938-dirtyuname -a
): 6.7.4-200.fc39.x86_64