Upgrade 16.2 to 17.1 with no internet on Director node fails overcloud_upgrade_prepare.sh script with registry.access.redhat.com/ubi8/pause message

Issue

• During upgrade from 16.2 to 17.1 when Director node has no internet connection (isolated environmnent), running overcloud_upgrade_prepare.sh tries to pull registry.access.redhat.com/ubi8/pause produces the following error

WARN[0000] failed, retrying in 1s ... (1/3). Error: Error initializing source docker://registry.access.redhat.com/ubi8/pause:latest: error pinging docker registry registry.access.redhat.com: Get "https://registry.access.redhat.com/v2/": read tcp 10.75.74.84:50232->23.50.113.175:443: read: connection reset by peer
WARN[0001] failed, retrying in 1s ... (2/3). Error: Error initializing source docker://registry.access.redhat.com/ubi8/pause:latest: error pinging docker registry registry.access.red
hat.com: Get "https://registry.access.redhat.com/v2/": read tcp 10.75.74.84:37608->23.50.113.184:443: read: connection reset by peer
WARN[0002] failed, retrying in 1s ... (3/3). Error: Error initializing source docker://registry.access.redhat.com/ubi8/pause:latest: error pinging docker registry registry.access.redhat.com: Get "https://registry.access.redhat.com/v2/": read tcp 10.75.74.84:37620->23.50.113.184:443: read: connection reset by peer
ERRO[0003] Error freeing pod lock after failed creation: no such file or directory
Error: error adding Infra Container: error pulling infra-container image: Error initializing source docker://registry.access.redhat.com/ubi8/pause:latest: error pinging docker registry registry.access.redhat.com: Get "https://registry.access.redhat.com/v2/": read tcp 10.75.74.84:37634->23.50.113.184:443: read: connection reset by peer

• This was tracked through RHBZ#2242605 which is solved by ERRATA.