Image pull from Quay fails due to incorrect backend storage hostname

Issue

• Unable to pull images from Red Hat Quay registry. The RHOCP cluster is being deployed through ACM. The bootstrap node displays this error:

  Mar 23 22:34:59 localhost systemd[1]: bootkube.service: Main process exited, code=exited, status=125/n/a
  Mar 23 22:34:59 localhost systemd[1]: bootkube.service: Failed with result 'exit-code'.
  Mar 23 22:35:04 localhost systemd[1]: bootkube.service: Service RestartSec=5s expired, scheduling restart.
  Mar 23 22:35:04 localhost systemd[1]: bootkube.service: Scheduled restart job, restart counter is at 7.
  Mar 23 22:35:04 localhost systemd[1]: Stopped Bootstrap a Kubernetes cluster.
  Mar 23 22:35:04 localhost systemd[1]: Started Bootstrap a Kubernetes cluster.
  Mar 23 22:35:17 localhost bootkube.sh[21422]: Rendering CEO Manifests...
  Mar 23 22:35:33 localhost bootkube.sh[21422]: Error: Error parsing image configuration: Error fetching blob: invalid status code from registry 502 (Bad Gateway)
  

• When manually pulling an image from the Quay, where used radosgw or noobaa is unmanaged object storage, returns the error parsing image configuration 502 (Bad Gateway):

  $ podman pull quay.apps.xxx.com/repository/alpine:latest
  Trying to pull quay.apps.xxx.com/repository/alpine:latest...
  Error: parsing image configuration: Error fetching blob: invalid status code from registry 502 (Bad Gateway)