Bug 1916007
| Summary: | olm skip range is set to the wrong range | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Carlos Eduardo Arango Gutierrez <carangog> |
| Component: | Node Feature Discovery Operator | Assignee: | Robin Cernin <rcernin> |
| Status: | CLOSED ERRATA | QA Contact: | Walid A. <wabouham> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.6.z | CC: | rcernin, sejug |
| Target Milestone: | --- | ||
| Target Release: | 4.6.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-09 20:00:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1916010 | ||
| Bug Blocks: | |||
|
Description
Carlos Eduardo Arango Gutierrez
2021-01-13 23:07:38 UTC
Hello Carlos, It is a valid bug. My understanding is this wouldn't upgrade to 4.1.0-> to 4.7.0, meaning it would miss upgrade in 4.6.z We saw same issue https://github.com/openshift/cluster-nfd-operator/pull/124/files and the issue comes from mis-understanding of olm.skipRange. I can see it's quite simple and has been assigned for a while without PR, hope you don't mind helping you :) Created https://github.com/openshift/cluster-nfd-operator/pull/127 Verified that https://github.com/openshift/cluster-nfd-operator/blob/release-4.6/manifests/olm-catalog/4.6/nfd.v4.6.0.clusterserviceversion.yaml#L34 now point to version 4.6: olm.skipRange: ">=4.3.0 <4.6.0" 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.20 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-2021:0675 |