We see lots of time connection timeout from Image registry

  4.17  

    Sometimes

There is no steps. We observer this lots of time in auto test runs    

https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/all/628986/87560329/87560435/log?item1Params=filter.eq.hasStats%3Dtrue%26filter.eq.hasChildren%3Dfalse%26filter.in.type%3DSTEP%26filter.in.status%3DFAILED%252CINTERRUPTED

  I0919 21:06:14.929763 300178 client.go:844] Error running /cli/oc --kubeconfig=/tmp/kubeconfig-1136279053 exec skopeo-1-4d7rl -n e2e-test-default-m4gnq -- skopeo --insecure-policy --src-tls-verify=false --dest-tls-verify=false copy --dcreds xxxxxx docker://quay.io/openshifttest/mysql:1.2.0 docker://image-registry.openshift-image-registry.svc:5000/e2e-test-default-m4gnq/mystream:latest:
  Getting image source signatures
  Copying blob sha256:ed88bae007bd9c42610e465ab436d60b2457b10b735a1bc8e5daba38f548c026
  Copying blob sha256:0a92fe4d3412152aa6b8e9d74163065fda41b4c77227f5f9c30b5fc8d0d16f26
  Copying blob sha256:f4ce92a382f8ee5355dddd6244487ef5246bdb325dc5dddd25d55afc14fc1a54
  Copying blob sha256:da05700210f681c47e021b8f3ce45f244f696854cfd656f0cd46e59cb8ca9b7d
  Copying blob sha256:feec96e115e3570a3306a7f9fe5bd8ad126e034793081ed6a8a7935f0a81da36
  time="2024-09-19T21:06:14Z" level=fatal msg="Error trying to reuse blob sha256:d4ba87bb7858f0dd4a60003f011338f3a58b87d0add985652856007fe5ca5034 at destination: Get "https://image-registry.openshift-image-registry.svc:5000/xxxxxxx": dial tcp 172.30.209.131:5000: i/o timeout"
  command terminated with exit code 1
  I0919 21:06:14.929934 300178 client.g

    showing connection timeout from image registry

    Image registry should not show connection timeout