The Heketi spec file changes the built-in value of the container image, but the value it sets refers to a rather old tag of the volmanager image. We should a) investigate if this is still needed and b) if so, update the tag to something more appropriate.
Summary: In OCS installation process, first we deploy deploy-heketi and gluster pods. We load the json into deploy-heketi, create the cluster based on json. Then run the setup-openshift-heketi-storage job which creates a job specification for the migration of the db. Then once the migration is complete, we deploy heketi. When heketi is ready, deploy-heketi is destroyed. The code change made for this bug is to change the image that is used for the migration of the db. There is no other way to test for this except interrupting the installation as mentioned in the previous comment and then manually observing the copy job specification. Regression testing is simpler: If the installation succeeds then it means the change in the image name hasn't impacted us in any way.
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, 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-2020:0621