Bug 1707679

Summary: The scc(CRD) resources can not be upgraded by 'oc patch' and 'oc edit'
Product: OpenShift Container Platform Reporter: scheng
Component: ocAssignee: Sally <somalley>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.0CC: aos-bugs, fdeutsch, jokerman, kincljc, markmc, mfojtik, mkhan, sttts, tnozicka
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:
: 1715290 (view as bug list) Environment:
Last Closed: 2019-10-16 06:28:32 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:
Bug Depends On:    
Bug Blocks: 1715290, 1764147    

Comment 3 Sally 2019-05-13 17:45:14 UTC 
This works:

$ cat patch.yaml
allowedUnsafeSysctls:
  - kernel.msg*

$ oc patch scc restricted -p "$(cat patch.yaml)" --type=merge
securitycontextconstraints.security.openshift.io/restricted patched


However, with move of SCC to CRD recently, edit might be broken, investigating.
Comment 4 Mark McLoughlin 2019-05-28 12:13:36 UTC 
Related thread, for reference: http://post-office.corp.redhat.com/archives/aos-devel/2019-May/msg00547.html
Comment 5 Stefan Schimanski 2019-08-02 10:41:07 UTC 
CRs will not get support for strategic merge patch. We cannot fix it this way. Why does oc user smp in the first place for this CRD? Moving to oc.
Comment 8 errata-xmlrpc 2019-10-16 06:28: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
Comment 9 Standa Laznicka 2019-12-13 12:37:49 UTC 
*** Bug 1783242 has been marked as a duplicate of this bug. ***