"Unable to pull OpenShift release image" on node console screen when ACM 2.7.2 is installing a disconnected SNO

OpenShift 4.12.5
ACM 2.7.2

Always

1. Install an OpenShift 4.12.5 and ACM 2.7.2
2. Apply assisted-installer-mirror-config
apiVersion: v1
kind: ConfigMap
metadata:
  name: assisted-installer-mirror-config
  namespace: assisted-installer
  labels:
    app: assisted-service
data:
  ca-bundle.crt:
      xxxxxxxxxxxxxxxxxxxxxxxxxxx
  registries.conf: |  
    unqualified-search-registries = ["registry.access.redhat.com", "docker.io"]    [[registry]]
      prefix = ""
      location = "quay.io/openshift-release-dev/ocp-release"  
      insecure = false      [[registry.mirror]]
        location = "registry.ocp4.example.com:8443/openshift/release-images"    [[registry]]
      prefix = ""
      location = "quay.io/openshift-release-dev/ocp-v4.0-art-dev"
      insecure = false      [[registry.mirror]]
        location = "registry.ocp4.example.com:8443/openshift/release"    [[registry]]
      prefix = "quay.io"
      location = "registry.ocp4.example.com:8443"    [[registry]]
      prefix = "registry.redhat.io"
      location = "registry.ocp4.example.com:8443"    [[registry]]
      prefix = "registry.access.redhat.com"
      location = "registry.ocp4.example.com:8443"    [[registry]]
      prefix = "registry.connect.redhat.com"
      location = "registry.ocp4.example.com:8443"    [[registry]]
      prefix = "docker.io"
      location = "registry.ocp4.example.com:8443"    [[registry]]
      prefix = "gcr.io"
      location = "registry.ocp4.example.com:8443"    [[registry]]
      prefix = "k8s.gcr.io"
      location = "registry.ocp4.example.com:8443" 
3.
# oc edit AgentServiceConfig/agent -n assisted-installer
  mirrorRegistryRef:
    name: assisted-installer-mirror-config
4. Create a disconnected cluster 

"Unable to pull OpenShift release image" on node console screen

Installation could pull image from private mirror registry

ACM console log, no further error

2023/4/4 13:23:24    Host: 00-00-00-38-38-38, reached installation stage Installing: bootstrap
2023/4/4 13:23:24    Host: 00-00-00-38-38-38, reached installation stage Starting installation: bootstrap
2023/4/4 13:23:24    Host 00-00-00-38-38-38: updated status from installing to installing-in-progress (Starting installation)
2023/4/4 13:23:16    Host 00-00-00-38-38-38: updated status from preparing-successful to installing (Installation is in progress)
2023/4/4 13:23:10    Updated status of the cluster to installing
2023/4/4 13:23:08    Host 00-00-00-38-38-38: updated status from preparing-for-installation to preparing-successful (Host finished successfully to prepare for installation)
2023/4/4 13:23:03    Host 00-00-00-38-38-38: New image status registry.redhat.io/multicluster-engine/assisted-installer-rhel8@sha256:e9cc2aaa551679627d56de22f6a9b5af044265172fe49d8c85930dbb6d1355b4. result: success. time: 14.88 seconds; size: 379.24 Megabytes; download rate: 26.72 MBps
2023/4/4 13:23:03    Host 00-00-00-38-38-38: New image status quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:44db200e247a760148aaf6d1c0f568e5a895942115c0bfaf57d424a97ead2425. result: success. time: 5.47 seconds; size: 487.95 Megabytes; download rate: 93.55 MBps
2023/4/4 13:23:03    Host 00-00-00-38-38-38: New image status quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:33b9e1b6e5c77f3e083119aa70ed79556540eb896e3b1f4f07792f213e06286a. result: success. time: 5.06 seconds; size: 512.50 Megabytes; download rate: 106.10 MBps
2023/4/4 13:23:03    Host 00-00-00-38-38-38: New image status quay.io/openshift-release-dev/ocp-release:4.12.5-x86_64. result: success. time: 12.69 seconds; size: 398.74 Megabytes; download rate: 32.96 MBps
2023/4/4 13:22:25    Cluster starting to prepare for installation
2023/4/4 13:22:20    Host 00-00-00-38-38-38: updated status from known to preparing-for-installation (Host finished successfully to prepare for installation)
2023/4/4 13:22:18    Host 00-00-00-38-38-38: set as bootstrap
2023/4/4 13:22:18    Updated status of the cluster to preparing-for-installation
2023/4/4 13:21:30    Updated status of the cluster to ready
2023/4/4 13:21:30    Cluster validation 'all-hosts-are-ready-to-install' is now fixed
2023/4/4 13:21:24    Host 00-00-00-38-38-38: updated status from insufficient to known (Host is ready to be installed)
2023/4/4 13:21:24    Host 00-00-00-38-38-38: validation 'ntp-synced' is now fixed
2023/4/4 13:20:40    Updated status of the cluster to insufficient
2023/4/4 13:20:40    Cluster validation 'machine-cidr-defined' is now fixed
2023/4/4 13:20:30    Cluster validation 'sufficient-masters-count' is now fixed
2023/4/4 13:20:30    
warning
 Cluster validation 'machine-cidr-defined' failed
2023/4/4 13:20:28    
warning
 Host 00-00-00-38-38-38: updated status from discovering to insufficient (Host cannot be installed due to following failing validation(s): Host couldn't synchronize with any NTP server)
2023/4/4 13:20:28    
warning
 Host 00-00-00-38-38-38: validation 'ntp-synced' that used to succeed is now failing
2023/4/4 13:20:23    Host 4e4bd155-877e-5f09-9fbe-2630fc0a8ff9: Successfully registered
2023/4/4 13:20:23    Host 4e4bd155-877e-5f09-9fbe-2630fc0a8ff9: updated status from binding to discovering (Waiting for host to send hardware details)
2023/4/4 13:20:00    Updated status of the cluster to pending-for-input
2023/4/4 13:19:59    Host 4e4bd155-877e-5f09-9fbe-2630fc0a8ff9: updated status from known-unbound to binding (Host is waiting to be bound to the cluster)
2023/4/4 13:19:54    Successfully registered cluster