+++ This bug was initially created as a clone of Bug #1995949 +++ +++ This bug was initially created as a clone of Bug #1995947 +++ +++ This bug was initially created as a clone of Bug #1995946 +++ Description of problem: olm.skipRange substitution does not work on 4.6. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Joep van Delft on 2021-08-20 09:18:47 UTC --- This is an admin bug to have a valid bug for 4.6. --- Additional comment from Joep van Delft on 2021-08-20 09:20:33 UTC --- This is an admin bug to have a valid one for 4.6 --- Additional comment from Joep van Delft on 2021-08-20 09:22:42 UTC --- This is an admin bug to have a valid bug in 4.6.
The chance of fixing this in 4.6 is quite low. We fix only critical issues at this point.
Unlikely this will get through. What is your motivation for fixing it in 4,6?
I'd say this is of some importance. ART wants to get more strict about failing substitutions. Note that openshift/cluster-nfd-operator#206 recently made it into 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.45 bug fix 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:3517