Best effort to move the OSL opeator:

package name to: logic-operator

operator name to: logic-operator.v1.37.0

 
Summary

In the operator bundle is used as the new package name logic-operator-rhel9 and this breaks the creation of Indexing image for OLM catalog. In the previous build the package name was logic-operator-rhel8 . Changes in include suffix for RHEL version bring changes in package name after rhel9 upgrades for all OSL images.

OLM Catalog Index Limitation: The Operator Lifecycle Manager (OLM) Catalog Index links an operator bundle to a channel based on the package name. If the package name changes (from logic-operator-rhel8 to logic-operator-rhel9 for a new version), it prevents the linking of different operator versions to the same channel.

Impact on Upgrades: This breaks the continuous upgrade stream. For example, linking OSL 1.36.0 (with package logic-operator-rhel8) and OSL 1.37.0 (with package logic-operator-rhel9) to the same "alpha" or "stable" channel is not possible, necessitating a manual, simplified upgrade path (removal of the old subscription/CSV and creation of a new one).
The proposed fix is to use a RHEL-neutral package name: logic-operator. Change the operator name to: logic-operator.v1.37.0

Environment

1.37.0.CR1

Steps to reproduce

1. Operator bundle build with replace value for `logic-operator-rhel8:1.36.0`
2. Run opm cli tool and add new bundle to indexing image with previous osl bundle

opm cli command fails with wrong replace value in logic-operator-rhel9 bundle

Workaround: In OSL Operator bundle in clusterserviceversion file, remove the line where is specified `replaces: `. The opm cli will pass. Now there will be 2 OSL operators in indexing images (catalog source) for 2 packages - for 1.36 it is logic-operator-rhel8 and for 1.37 it is logic-operator-rhel9