Bug 1345805 - Output info is not correct when debug a pod with invalid node name.
Summary: Output info is not correct when debug a pod with invalid node name.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.2.1
Assignee: Fabiano Franz
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On: 1330050
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-13 08:46 UTC by Xingxing Xia
Modified: 2016-07-20 19:37 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Previously if `oc debug` was used against an invalid node the error message did not clearly indicate the node was invalid. The error message has been updated to indicate that an invalid node was provided.
Clone Of: 1330050
Environment:
Last Closed: 2016-07-20 19:37:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1466 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise 3.2.1.9 security and bug fix update 2016-07-20 23:37:14 UTC

Comment 2 Fabiano Franz 2016-07-04 18:33:30 UTC
This is now in OSE master.

Comment 3 Yanping Zhang 2016-07-05 06:20:11 UTC
Wait for a new puddle containing the fix to check the bug.

Comment 8 Yanping Zhang 2016-07-07 01:57:39 UTC
Checked on ose 3.2 :
# oc version
oc v3.2.1.5-1-g71b9ccf
kubernetes v1.2.0-36-g4a3f9c5

# oc debug dc/database --node-name=invalidnode -- /bin/env
Debugging with pod/database-debug, original command: <image entrypoint>
Waiting for pod to start ...

Removing debug pod ...
error: unable to create the debug pod "database-debug" on node "invalidnode"

The bug has been fixed, so move it to Verified.

Comment 10 errata-xmlrpc 2016-07-20 19:37:23 UTC
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-2016:1466


Note You need to log in before you can comment on or make changes to this bug.