Bug 1723358
| Summary: | `oc` client exits while watching resources and using a custom output | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Shivkumar Ople <sople> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED DUPLICATE | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.11.0 | CC: | aos-bugs, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-24 11:56:43 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: | |||
*** This bug has been marked as a duplicate of bug 1709456 *** |
Description of problem: When using the openshift client to follow/watch resources, the `oc` client exits prematurely with an exit code of 0 when new events occur and an output format is defined. Version-Release number of selected component (if applicable): v3.11.104 How reproducible: Always Steps to Reproduce: --> Login to your OpenShift cluster using the v3.11.104 `oc` client as a cluster-admin (just to make things easier) and run the following command: # oc get pods -n default -o go-template='{{.metadata.name}}' -w --> Open another terminal and login to the same OpenShift cluster and delete any of the pods in the `default` namespace. Actual results: oc Command is exiting Expected results: oc client command should not exit Additional info: The above steps to reproduce should show that the original watching client exits prematurely rather than continue to follow the pod events. The following/watching behavior only seems to exit prematurely when any -o (output format) is supplied while watching any resource using the OpenShift client. Older clients such as v3.6.173.0.21 handle the use of -o (output format) while watching resource properly and do not immediately exit once new events are observed.