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

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

XMLWordPrintable

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

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      * Previously, Zscaler traffic scanning caused a pull-progress timeout in the CRI-O container engine, creating an infinite loop and image pull failure. As a result, users were unable to pull images. With this release, the pull progress timeout is now 20 seconds, disabling the timeout and progress output for image pulls and reducing the customer image pull timeout issues with Zscaler.(link:https://issues.redhat.com/browse/OCPBUGS-54665[OCPBUGS-54665])
      Show
      * Previously, Zscaler traffic scanning caused a pull-progress timeout in the CRI-O container engine, creating an infinite loop and image pull failure. As a result, users were unable to pull images. With this release, the pull progress timeout is now 20 seconds, disabling the timeout and progress output for image pulls and reducing the customer image pull timeout issues with Zscaler.(link: https://issues.redhat.com/browse/OCPBUGS-54665 [ OCPBUGS-54665 ])
    • 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:

              andreibytes Andrei Capi (Inactive)
              rhn-support-shouming Shouming Sun
              None
              None
              Aditi Sahay Aditi Sahay
              None
              Votes:
              2 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: