Bug 1969230 - service-ca pod does not run when restricted SCC is changed
Summary: service-ca pod does not run when restricted SCC is changed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: service-ca
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Stefan Schimanski
QA Contact: scheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-08 03:09 UTC by Matt Bargenquast
Modified: 2022-02-23 20:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-23 08:17:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matt Bargenquast 2021-06-08 03:09:05 UTC 
Description of problem:

When the "restricted" SCC is changed to have a "runAsUser" value of "RunAsAny" it results in the service-ca pod not starting up and remaining in a "CreateContainerConfigError" state. 

The pod yaml notes:
container has runAsNonRoot and image will run as root (pod: "service-ca-78d76c8f96-9d94g_openshift-service-ca(164c78e4-4e79-47d3-afca-53358e43e70b)", container: service-ca-controller)

Version-Release number of selected component (if applicable):

4.7.11

How reproducible:

Always

Steps to Reproduce:
1. Set the "restricted" SCC to have a "runAsUser" value of "RunAsAny"
2. Restart the service-ca pod.
3. Pod will not start up.
Comment 1 Standa Laznicka 2021-06-08 07:01:16 UTC 
https://docs.openshift.com/container-platform/4.7/authentication/managing-security-context-constraints.html
Comment 3 Standa Laznicka 2022-02-23 08:17:49 UTC 
The docs in https://bugzilla.redhat.com/show_bug.cgi?id=1969230#c1 say you should not change the default SCCs.
Comment 4 Standa Laznicka 2022-02-23 08:18:27 UTC 
Also, your bug report is different from the original.
Note You need to log in before you can comment on or make changes to this bug.