Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-54658

The default value of 'pull-progress-timeout' is too small

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.16
    • Node / Kubelet
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      After introducing `pull-progress-timeout` in https://issues.redhat.com/browse/OCPBUGS-33075, customer experiences timeout when pulling images because they use zscaler and scans all tranfers. This results on a 10-15 seconds minimum to send a bit. When the client disconnects - in this particular case, crio- the scan is abort. This leads to a loop and the customer is unable to pull image at all. This blocks customer updating to 4.16.37 + since no Red Hat image can be pulled.

Discussion thread: https://redhat-internal.slack.com/archives/CK1AE4ZCK/p1742847666745759

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Modify the default value to 20s.

      Additional info:

              sgrunert@redhat.com Sascha Grunert
              rhn-support-shouming Shouming Sun
              None
              None
              Cameron Meadors Cameron Meadors
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: