oc client exits while watching resources and using a custom output

Solution Verified - Updated -

Issue

  • 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.
  • Problematic versionv3.11.104 oc 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.

Environment

  • OpenShift Container Platform
    • 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content