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

4.17 oc exec doesn't work through a proxy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.17.z
    • oc
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the `attach`, `oc exec`, and `port-forward` commands received an error if you ran the commands through a proxy. With this release, a patch applied to kubectl ensures kubectl can handle any proxy errors with these commands, so that the commands run as expected. (link:https://issues.redhat.com/browse/OCPBUGS-43696[*OCPBUGS-43696*])
      Show
      * Previously, the `attach`, `oc exec`, and `port-forward` commands received an error if you ran the commands through a proxy. With this release, a patch applied to kubectl ensures kubectl can handle any proxy errors with these commands, so that the commands run as expected. (link: https://issues.redhat.com/browse/OCPBUGS-43696 [* OCPBUGS-43696 *])
    • Bug Fix
    • Done

      Description of problem:

      Running `oc exec` through a proxy doesn't work

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

      4.17.1

      How reproducible:

      100%

      Additional info:

      Looks to have been fixed upstream in https://github.com/kubernetes/kubernetes/pull/126253 which made it into 1.30.4 and should already be in 1.31.1 as used in 4.18.

Likely just needs to bump oc to that version or later.  

              aguclu@redhat.com Arda Guclu
              rhn-support-sdodson Scott Dodson
              ying zhou ying zhou
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: