Description of problem: oc debug with not-exist node, 3.5 output is clear 'Error from server (NotFound): nodes "invalidnode" not found', but 3.6 output is 'error: unable to create the debug pod "mydc-debug" on node "invalidnode"', which cannot tell clearly whether the node is an existent node that has problem "to create the debug pod", or the node name is a non-existent node Version-Release number of selected component (if applicable): v3.6.153 How reproducible: Always Steps to Reproduce: 1. $ oc run mydc --image=aosqe/hello-openshift 2. $ oc debug dc/mydc --node-name="notexist" wait and check output Actual results: """ Debugging with pod/python35-debug, original command: container-entrypoint /usr/libexec/s2i/run Waiting for pod to start ... Removing debug pod ... error: unable to create the debug pod "mydc" on node "notexist" """ Expected results: Message should be clear, eg. 3.5 cli output 'Error from server (NotFound): nodes "notexist" not found' Additional info:
Origin PR: https://github.com/openshift/origin/pull/16387
Wait for verify when PR is merged to OCP.
Verified on latest OCP: oc v3.7.0-0.131.0 # oc debug dc/mydc --node-name="notexist" Error from server (NotFound): nodes "notexist" not found
Reverted in bug 1505698