Description of problem: - lastHeartbeatTime: "2020-05-20T12:26:32Z" lastTransitionTime: "2020-05-20T11:48:54Z" message: |- KubeVirt is not available: An error occurred during deployment: unable to create config map &ConfigMap{ObjectMeta:{kubevirt-cpu-plugin-configmap openshift-cnv 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[app.kubernetes.io/managed-by:kubevirt-operator] map[kubevirt.io/install-strategy-identifier:8b96556cbfff6161782480cef7f5eb410d65be18 kubevirt.io/install-strategy-registry:registry-proxy.engineering.redhat.com/rh-osbs kubevirt.io/install-strategy-version:sha256:6935af5e1b7464190254b9b8f86d6af0afefe987b670eb0050cb73883cbbf132] [] [] []},Data:map[string]string{cpu-plugin-configmap.yaml: obsoleteCPUs: - "486" - "pentium" - "pentium2" - "pentium3" - "pentiumpro" - "coreduo" - "n270" - "core2duo" - "Conroe" - "athlon" - "phenom" minCPU: "Penryn",},BinaryData:map[string][]byte{},}: configmaps "kubevirt-cpu-plugin-configmap" already exists reason: KubeVirtNotAvailable status: "False" type: Available Version-Release number of selected component (if applicable): registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-hco-bundle-registry:v2.3.0-226 OCP-4.5 How reproducible: 100% Steps to Reproduce: 1. Try to deploy CNV 2. 3. Actual results: Seeing above error Expected results: CNV deployed successfully Additional info:
This probably comes from https://github.com/kubevirt/kubevirt/pull/3133 that adds to virt-operator the code to create kubevirt-cpu-plugin-configmap which was previously on ssp-operator. Now the question is if we have to change something on the HCO side regarding how we trigger ssp-operator or if we are simply consuming a wrong version of ssp-operator.
We are working on a fix which deletes labeller from ssp operator.
Fixed by: https://github.com/MarSik/kubevirt-ssp-operator/pull/156
Verified on CNV-2.4.0, OCP: 4.5.0-rc.2, SSP build 58: CNV is deployed, kubevirt-cpu-plugin-configmap is successfully created.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3194