Community catalogSource pod should use the production base image

[mrhillsman]

Description of problem:
Should use the production base image for the community CatalogSource pods.

[root@preserve-olm-env data]# oc exec community-operators-5cl5r -- cat /etc/redhat-release
cat: can't open '/etc/redhat-release': No such file or directory
[root@preserve-olm-env data]# oc exec certified-operators-68dp7 -- cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.8 (Maipo)

Version-Release number of selected component (if applicable):
Cluster version is 4.6.0-0.nightly-2020-08-04-035157

How reproducible:
Always

Steps to Reproduce:

1. Install OCP 4.6.
2. Check the CatalogSource pod if use the production image.

Actual results:
Community operator doesn't use the production image.
[root@preserve-olm-env data]# oc exec certified-operators-68dp7 -- cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.8 (Maipo)
[root@preserve-olm-env data]# oc exec community-operators-5cl5r -- cat /etc/redhat-release
cat: can't open '/etc/redhat-release': No such file or directory

Expected results:
I know these operators provided by this community image from the Community. But, it will be release as OCP production too. We should use the production image for it.

Additional info:
Copied from https://bugzilla.redhat.com/show_bug.cgi?id=1865815

[jianzhangbjz]

@mrhillsman It has been fixed, see: https://bugzilla.redhat.com/show_bug.cgi?id=1865815#c5. So, can we close this issue? Thanks!

[mrhillsman]

Thx @jianzhangbjz