Description of problem: SSP CRD names were changed from 2.3 to 2.4, but the old CRDs are not removed when deleting the old version. That creates two set of CRDs with different names, and blocks querying the DRs. Version-Release number of selected component (if applicable): 2.3 How reproducible: Steps to Reproduce: 1. deploy CNV 2.3 2. upgrade to CNV 2.4 3. query SSP CRs, e.g. ``` # oc get kubevirtnodelabellerbundles --all-namespaces No resources found. # oc get kubevirtmetricsaggregations --all-namespaces No resources found. # oc get kubevirtcommontemplatesbundles --all-namespaces No resources found. # oc get kubevirttemplatevalidators --all-namespaces No resources found. ``` Actual results: 1. No resource found 2. When querying the CRDs, K8s returns two result for each CRD Expected results: 1. CR is returned 2. When querying an SSP CRD, only one result is returned Additional info:
Should be solved along with https://bugzilla.redhat.com/show_bug.cgi?id=1832283. Once 283 is verified, this should be retested
Verified: OCP 4.5.0-rc.6, upgrade from 2.3.0 - > 2.4.0 (SSP v2.4.0-66) ends successfully. SSP CRs and CRDs exist on the clustser: $ oc get crd -n openshift-cnv|grep ssp kubevirtcommontemplatesbundles.ssp.kubevirt.io 2020-07-08T11:06:33Z kubevirtmetricsaggregations.ssp.kubevirt.io 2020-07-08T11:06:34Z kubevirtnodelabellerbundles.ssp.kubevirt.io 2020-07-08T11:06:34Z kubevirttemplatevalidators.ssp.kubevirt.io 2020-07-08T11:06:34Z $ oc get kubevirtnodelabellerbundles --all-namespaces NAMESPACE NAME AGE openshift-cnv node-labeller-kubevirt-hyperconverged 111m $ oc get kubevirtmetricsaggregations --all-namespaces NAMESPACE NAME AGE openshift-cnv metrics-aggregation-kubevirt-hyperconverged 111m $ oc get kubevirtcommontemplatesbundles --all-namespaces NAMESPACE NAME AGE openshift common-templates-kubevirt-hyperconverged 111m $ oc get kubevirttemplatevalidators --all-namespaces NAMESPACE NAME AGE openshift-cnv template-validator-kubevirt-hyperconverged 111m
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