Bug 2065085 - Upgrade OpenShift 4.10.3 to 4.10.4 fails with sandboxed containers operator installed
Summary: Upgrade OpenShift 4.10.3 to 4.10.4 fails with sandboxed containers operator i...
Keywords:
Status: CLOSED DUPLICATE of bug 2057545
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: MCO Team
QA Contact: Rio Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-17 10:33 UTC by Sascha Grunert
Modified: 2022-03-22 11:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-22 10:33:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Francesco Giudici 2022-03-22 10:33:25 UTC 
This issue is known, a workaround is presented in release notes:
https://docs.openshift.com/container-platform/4.10/sandboxed_containers/sandboxed-containers-release-notes.html#sandboxed-containers-1-2-known-issues

Another bug is tracking the issue, setting this as duplicate.

*** This bug has been marked as a duplicate of bug 2057545 ***
Comment 2 Greg Kurz 2022-03-22 11:04:00 UTC 
(In reply to Francesco Giudici from comment #1)
> This issue is known, a workaround is presented in release notes:
> https://docs.openshift.com/container-platform/4.10/sandboxed_containers/
> sandboxed-containers-release-notes.html#sandboxed-containers-1-2-known-issues
> 
> Another bug is tracking the issue, setting this as duplicate.
> 
> *** This bug has been marked as a duplicate of bug 2057545 ***

BTW, even if OSC is the new kid in town, the failing component is the
MCO pod, which should better describe the privileges it needs so that
the admission process doesn't choose the OSC SCC for it.

Changing the component accordingly for the records.
Note You need to log in before you can comment on or make changes to this bug.