Closed nuwang closed 6 months ago
Thanks @nuwang for letting us know!
The problem is that following the instructions on the catalog page, makes OLM to install HCO and the other components on the wrong namespace. The wrong namespace is operators
while it should be installed at kubevirt-hyperconverged
.
@orenc1 - do you know what may cause it? I suspect it's olm/operator-sdk issue.
@nunnatsa Thanks for the quick response. Ran into the namespace issue too, but even after installing in the kubevirt-hyperconverged
namespace, this still happens with v1.10.0 but works fine with v1.9.0.
Yes, after working with @orenc1 on it - we found that it's a real bug in HCO code. Working on a solution now
@nuwang hi.
Version v1.10.1 fixes this issue.
/kind bug
What happened: Installing hco-operator v1.10.0 via OperatorHub throws a nil pointer exception and does not start up.
How to reproduce it (as minimally and precisely as possible):
Install v1.10.0 of HCO on EKS or upgrade from v1.9.0 to v1.10.0
Anything else we need to know?:
Stack trace
Image version:
quay.io/kubevirt/hyperconverged-cluster-operator@sha256:9a5f03e3fa84aaa07cc334036083a66ffbd467a8e1a1a9acfdfaed733873e6fe
v1.9.0 can be installed and works as expected.
Environment:
oc get csv -n kubevirt-hyperconverged
): v1.10.0kubectl version
): Client Version: v1.28.3 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.27.8-eks-8cb36c9Fixing process