Bug 1345805
| Summary: | Output info is not correct when debug a pod with invalid node name. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> |
| Component: | oc | Assignee: | Fabiano Franz <ffranz> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.1 | CC: | aos-bugs, ffranz, jokerman, mmccomas, tdawson, trankin, wsun, yanpzhan |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 3.2.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1330050 | Environment: | |
| Last Closed: | 2016-07-20 19:37:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1330050 | ||
| Bug Blocks: | |||
|
Comment 2
Fabiano Franz
2016-07-04 18:33:30 UTC
Wait for a new puddle containing the fix to check the bug. 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. 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 |