Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1745532

Summary: `oc get --ignore-not-found -f -` does not behave like `oc get --ignore-not-found kind/name.. `
Product: OpenShift Container Platform Reporter: Michal Fojtik <mfojtik>
Component: ocAssignee: Mike Dame <mdame>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jokerman, jupierce, maszulik, mdame, mfojtik, tnozicka, yinzhou
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1727917 Environment:
Last Closed: 2019-10-16 06:37:32 UTC Type: ---
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:    
Bug Blocks: 1727917    

Comment 1 Michal Fojtik 2019-08-26 10:33:08 UTC
Mike are you going to backport this to 4.2 ?

Comment 3 Maciej Szulik 2019-08-29 13:28:44 UTC
Current bump is in https://github.com/openshift/oc/pull/79

Comment 5 zhou ying 2019-09-03 02:26:12 UTC
Confirmed with oc extracted from payload 4.2.0-0.nightly-2019-09-02-172410, the issue has fixed:

[root@dhcp-140-138 ~]# oc get -n openshift-monitoring --ignore-not-found secrets/grafana-tls secrets/grafana-proxy-missing secrets/grafana-config
NAME             TYPE                DATA   AGE
grafana-tls      kubernetes.io/tls   2      23h
grafana-config   Opaque              1      23h


[root@dhcp-140-138 ~]# oc get -f search.yaml --ignore-not-found
NAME             TYPE                DATA   AGE
grafana-tls      kubernetes.io/tls   2      23h
grafana-config   Opaque              1      23h

Comment 6 errata-xmlrpc 2019-10-16 06:37:32 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-2019:2922