Bug 1946831

+++ This bug was initially created as a clone of Bug #1945026 +++

Description of problem (please be detailed as possible and provide log
snippests):
OSUS operator keep restart due to missing env OPERAND_IMAGE.(Should be RELATED_IMAGE_OPERAND now)
# ./oc get po
NAME                                      READY   STATUS             RESTARTS   AGE
updateservice-operator-7c485c9bf4-t9t26   0/1     CrashLoopBackOff   6          7m38s

# ./oc logs updateservice-operator-7c485c9bf4-t9t26
2021-03-31T08:57:37.340Z	INFO	cmd	Operator Version: d0d2b8409e3ebf903758efc3627fa3effb12450c
2021-03-31T08:57:37.341Z	INFO	cmd	Go Version: go1.14.12
2021-03-31T08:57:37.341Z	INFO	cmd	Go OS/Arch: linux/amd64
I0331 08:57:38.392818       1 request.go:645] Throttling request took 1.034694457s, request: GET:https://172.30.0.1:443/apis/project.openshift.io/v1?timeout=32s
2021-03-31T08:57:39.752Z	INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": ":8080"}
2021-03-31T08:57:39.752Z	ERROR	cmd		{"error": "Must set envvar OPERAND_IMAGE"}
github.com/go-logr/zapr.(*zapLogger).Error
	/remote-source/app/vendor/github.com/go-logr/zapr/zapr.go:132
main.main
	/remote-source/app/main.go:101
runtime.main
	/usr/lib/golang/src/runtime/proc.go:203

It should be related with the osus operand name update in csv to fix osbs auto replacement days ago.

Version of all relevant components (if applicable):
OSUS operator image: v4.6.0-6
OSUS image: v4.6.0-9
Bundle image: v1.0-23

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
always

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:
yes

Steps to Reproduce:
1. Install osus operator
2.
3.


Actual results:
OSUS operator install fail.

Expected results:
Operator should be installed successfully.


Additional info: