Hide Forgot
$ oc --config=/tmp/kubeconfig debug node/ip-10-0-146-187.us-east-2.compute.internal -- false Starting pod/ip-10-0-146-187us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` Removing debug pod ... $ echo $? 0 As you can see the command `false` has been executed but exit code of `oc` is still `0`. – Client Version: v4.2.0
https://github.com/openshift/oc/pull/277 for multiple bzs including this
Confirmed with latest oc client, the issue has fixed: [root@dhcp-140-138 ~]# oc version -o yaml clientVersion: buildDate: "2020-02-13T22:50:14Z" compiler: gc gitCommit: 5d7a12f03389b03b651f963cb5ee8ddfa9cff559 gitTreeState: clean gitVersion: v4.4.0 goVersion: go1.13.4 major: "" minor: "" platform: linux/amd64 [root@dhcp-140-138 ~]# oc debug node/ip-xxxxx -- /bin/missing param1 param2 Starting pod/ip-xxxxx-debug ... To use host binaries, run `chroot /host` Removing debug pod ... error: container create failed: time="2020-02-14T02:34:39Z" level=error msg="container_linux.go:346: starting container process caused \"exec: \\\"/bin/missing\\\": stat /bin/missing: no such file or directory\"" container_linux.go:346: starting container process caused "exec: \"/bin/missing\": stat /bin/missing: no such file or directory" [root@dhcp-140-138 ~]# echo $? 1
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, 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:0581