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.