You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploy an OCP 4.9 cluster (virtual cluster with kcli in my case)
Add appropriate CatalogSource to access the 1.1.0 operator image
Start installation
Describe the results you received:
The installation seems to complete in less than 30 seconds : the web UI notifies that the operator is installed and ready to be used. But then after a couple of seconds, the operator's status transitions to "Installing". This continues again and again until the cluster sets a CrashLoopBackOff status and installation is canceled.
Describe the results you expected:
The installation succeeds and I can use Kata in the cluster.
Additional information you deem important (e.g. issue happens only occasionally):
This is reproducible 100% in my setup.
Here's the console output of the pod that fails in a loop during installation :
I0909 11:42:30.555078 1 request.go:645] Throttling request took 1.089807089s, request: GET:https://172.30.0.1:443/apis/flowcontrol.apiserver.k8s.io/v1beta1?timeout=32s
2021-09-09T11:42:37.952Z INFO controller-runtime.metrics metrics server is starting to listen {"addr": "127.0.0.1:8080"}
I0909 11:42:40.603369 1 request.go:645] Throttling request took 2.644938699s, request: GET:https://172.30.0.1:443/apis/whereabouts.cni.cncf.io/v1alpha1?timeout=32s
2021-09-09T11:42:46.355Z ERROR setup unable to use discovery client {"error": "unable to retrieve the complete list of server APIs: subresources.kubevirt.io/v1: the server is currently unable to handle the request, subresources.kubevirt.io/v1alpha3: the server is currently unable to handle the request, upload.cdi.kubevirt.io/v1alpha1: the server is currently unable to handle the request, upload.cdi.kubevirt.io/v1beta1: the server is currently unable to handle the request"}
github.com/go-logr/zapr.(*zapLogger).Error
/remote-source/deps/gomod/pkg/mod/github.com/go-logr/zapr@v0.2.0/zapr.go:132
main.main
/remote-source/app/main.go:78
runtime.main
/usr/lib/golang/src/runtime/proc.go:204
Output of oc describe kataconfig <your-kataconfig>:
I've switched to using the QE optional operators repo to pull the operator since then and I can't reproduce the issue anymore. I guess this was a transient issue related to my previous setup, hence closing.
Description
Steps to reproduce the issue:
Describe the results you received:
The installation seems to complete in less than 30 seconds : the web UI notifies that the operator is installed and ready to be used. But then after a couple of seconds, the operator's status transitions to "Installing". This continues again and again until the cluster sets a CrashLoopBackOff status and installation is canceled.
Describe the results you expected:
The installation succeeds and I can use Kata in the cluster.
Additional information you deem important (e.g. issue happens only occasionally):
This is reproducible 100% in my setup.
Here's the console output of the pod that fails in a loop during installation :
Output of
oc describe kataconfig <your-kataconfig>
:N/A
Additional environment details (platform, options, etc.):
CatalogSource for the operator image
The text was updated successfully, but these errors were encountered: