Description of problem: olm.skipRange is not set for product builds. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verify Result: oc describe clusterserviceversion special-resource-operator.4.9.0-202108261630 -n openshift-operators | grep -B5 -A5 olm.skipRange categories: AI/Machine Learning, Drivers and plugins, Networking, Storage description: The special resource operator is an orchestrator for resources in a cluster required to deploy special hardware and software. Examples inc... olm.operatorGroup: global-operators olm.operatorNamespace: openshift-operators olm.skipRange: >=4.6.0 <4.9.0-202108261630 olm.targetNamespaces: operatorframework.io/properties: {"properties":[{"type":"olm.gvk","value":{"group":"sro.openshift.io","kind":"SpecialResource","version":"v1beta1"}},{"type":"olm.package",... operators.operatorframework.io/builder: operator-sdk-v1.2.0 operators.operatorframework.io/project_layout: go.kubebuilder.io/v2
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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/RHSA-2021:3759