Open ruivieira opened 7 months ago
Looks like marketplace operator is not able to resync the pull secret because if you check the pod description you will find auth error. Easy fix for it delete all the pods from openshift-marketplace
which will allow to have new pods which have updated pull-secret.
$ oc delete pods --all -n openshift-marketplace
Looks like there was issue on OLM side https://issues.redhat.com/browse/OCPBUGS-31645 have more info and https://github.com/operator-framework/operator-lifecycle-manager/pull/3197 upstream PR which is merged. So hopefully when we have latest version of OLM it will be fixed automatic.
Thanks for the update @praveenkumar!
I faced the same problem. After updating the version, Operator Hub disappeared. My environment is macOS 14.4 Intel based.
I faced the same problem. After updating the version, Operator Hub disappeared. My environment is macOS 14.4 Intel based.
You will need tihs workaround https://github.com/crc-org/crc/issues/4109#issuecomment-2042497411 until at least the next crc release.
Also faced this on Windows. I deleted the Pods that were saying crashloopback and reload/saved YAML in openshift-marketplace project to get OperatorHub working again.
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
NOTE: despite this status, crc seems to be working fine.
CRC config
Host Operating System
Steps to reproduce
crc
2.33, upgrade to 2.34crc stop ; crc delete --cache
crc setup
crc start
Expected
OperatorHub to be available
Actual
OperatorHub empty with no items.
community-operators
,redhat-operators
,redhat-marketplace
,certified-operators
pods crashing with incorrect SHA value errors.Logs
No logs collected. Errors detect in the cluster, not crc directly.
This was fixed by disabling and renabling the sources, eg.