Created attachment 1728885 [details] Screenshot(metering-CRD) Description of problem: When metering-operator is upgraded from 4.4 -> 4.5 -> 4.6 , it fails. The install plan fails with the following error: ~~~ error validating existing CRs agains new CRD's schema: hivetables.metering.openshift.io: error validating custom resource against new schema &apiextensions.CustomResourceValidation{OpenAPIV3Schema:(*apiextensions.JSONSchemaProps)(0xc0058f6400)}: [].status.partitions: Invalid value: "null": status.partitions in body must be of type array: "null" ~~~ The error indicates that there are objects on the cluster (hivetables) that don’t validate against the schema of the updated CRD, so it’s not safe to apply the CRD update. It’s might be an accidental backwards-incompatible change in the hivetables schema. Version-Release number of selected component (if applicable): OCP 4.6.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: New csv gets stuck in pending state, where all the CR goes into unknown state. oc get csv NAME DISPLAY VERSION REPLACES PHASE metering-operator.4.6.0-202010200139.p0.2 Metering 4.6.0-202010200139.p0 metering-operator.4.5.0-202010170258.p0 Pending Expected results: Metering operator successfully upgrades to 4.6.0-202010200139.p0 Additional info:
Created attachment 1728886 [details] installplan.yml
Created attachment 1728887 [details] csv.yml
Created attachment 1728888 [details] subscriptions.yml
Created attachment 1728889 [details] operatorgroup.yml
Created attachment 1729074 [details] all-hivetables.yaml
verified with the latest 4.6
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 (OpenShift Container Platform 4.6.9 extras update), 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/RHBA-2020:5616