Bug 1614200 - Cannot output json format when oc edit with -o json options
Summary: Cannot output json format when oc edit with -o json options
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Juan Vallejo
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-09 07:57 UTC by wewang
Modified: 2018-10-11 07:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-11 07:24:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:24:34 UTC

Description wewang 2018-08-09 07:57:23 UTC 
Description of problem:
Output yaml format when oc edit with -o json option

Version-Release number of selected component (if applicable):
oc v3.11.0-0.11.0

How reproducible:
always

Steps to Reproduce:
1.Create a build 
$ oc new-build openshift/ruby:2.3~https://github.com/sclorg/ruby-ex.git
2.Edit bc with -o json option
$oc edit bc/ruby-ex -o json
3.

Actual results:
Output is a yaml format, not json format

Expected results:
shoud output json format 

Additional info:
Comment 1 Juan Vallejo 2018-08-09 15:27:45 UTC 
This was fixed upstream in https://github.com/kubernetes/kubernetes/pull/66225
Will pick into Origin
Comment 2 Juan Vallejo 2018-08-09 15:48:33 UTC 
Origin PR: https://github.com/openshift/origin/pull/20589
Comment 3 Juan Vallejo 2018-08-13 18:00:40 UTC 
PR has merged. Moving to MODIFIED
Comment 6 wewang 2018-08-27 10:00:58 UTC 
verified in openshift v3.11.0-0.22.0
oc v3.11.0-0.22.0
Comment 8 errata-xmlrpc 2018-10-11 07:24:08 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-2018:2652
Note You need to log in before you can comment on or make changes to this bug.