Bug 1996051

Summary:	[SCC] openshift-apiserver degraded when a SCC with high priority is created
Product:	OpenShift Container Platform	Reporter:	Sergiusz Urbaniak <surbania>
Component:	openshift-apiserver	Assignee:	Sergiusz Urbaniak <surbania>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.9	CC:	aos-bugs, gvanderp, mfojtik, mjudeiki, oarribas, surbania, xxia
Target Milestone:	---
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	EmergencyRequest
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1960680	Environment:
Last Closed:	2021-09-29 12:06:50 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:	1996045
Bug Blocks:

Comment 2 Xingxing Xia 2021-09-22 08:48:05 UTC

Verified in 4.6.0-0.nightly-2021-09-21-161128:
Create above k10-k10 SCC. Then delete one pod under openshift-apiserver project. Check the new created pod, it can be Running.
Then check the YAML of all pods under openshift-apiserver project, they all set 'runAsUser: 0' under container 'openshift-apiserver' and the init container 'fix-audit-permissions'

Comment 5 errata-xmlrpc 2021-09-29 12:06:50 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 (OpenShift Container Platform 4.6.46 bug fix update), 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-2021:3643