Description of problem: `oc debug` command can't work Version-Release number of selected component (if applicable): [root@dhcp-140-138 ~]# oc version Client Version: 4.6.0-202007221854.p0-5f270d5 How reproducible: Always Steps to Reproduce: 1. `oc debug node/ip-xxxx.internal` 2. `oc debug pod/podname` Actual results: 1-2. the command exit without create debug pod. Expected results: 1. Should create debug pod . Additional info: Client Version: 4.6.0-202005061824-29e9a33 works well
It looks like this will be fixed in the next available oc nightly build by the changes in https://github.com/openshift/oc/pull/502, so moving this to modified
Confirmed with latest oc client, the issue has fixed: [root@dhcp-140-138 ~]# oc version --client Client Version: 4.6.0-202007282157.p0-49e8811 [root@dhcp-140-138 ~]# oc debug node/ip-xxxx.compute.internal Starting pod/ip-xxxx-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.151.144 If you don't see a command prompt, try pressing enter. sh-4.2# chroot /host sh-4.4# exit exit sh-4.2# exit exit Removing debug pod ...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196