-
Bug
-
Resolution: Duplicate
-
Major
-
3.3.0.GA
-
False
-
None
-
False
-
-
Bug Fix
-
Rejected
-
-
Synced from Eclipse Che issue
https://github.com/eclipse/che/issues/21824
Describe the bug
- Install Eclipse Che 7.56.0 via OperatorHub
- Create default CR (container build is disabled by default)
- Start a Getting Started sample
- ERROR: Failed to start the workspace spring-petclinic, reason: Failed to update workspace 'spring-petclinic'. Unable to patch devworkspace: admission webhook "mutate.devworkspace-controller.svc" denied the request: user is not permitted use the container-build SCC
Che version
7.56@latest
Steps to reproduce
See description
Expected behavior
Workspace started without problems
Runtime
OpenShift
Screenshots
Installation method
OperatorHub
Environment
Linux
Eclipse Che Logs
No response
Additional context
Reproducible against OpenShift 4.10.36 RHPDS cluster
Release notes text
A regression has been introduced in Eclipse Che 7.56 so that when installing Che on OpenShift using operator hub, workspaces started from Getting Started section of User Dashboard would fail to start with the error 'user is not permitted use the container-build SCC'.
- duplicates
-
CRW-3554 Dashboard ignores "disableContainerBuildCapabilities: true" CheCluster property when there is "openShiftSecurityContextConstraint: container-build"
- Closed
- links to