Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1752905

Summary: Kuryr unable to annotate pods in namespaces without `openshift.io/run-level` annotation
Product: OpenShift Container Platform Reporter: Michał Dulko <mdulko>
Component: NetworkingAssignee: Michał Dulko <mdulko>
Networking sub component: kuryr QA Contact: GenadiC <gcheresh>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: itbrown
Version: 4.2.0   
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:41:28 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:

Description Michał Dulko 2019-09-17 14:27:42 UTC
Description of problem:
Kuryr is missing permissions to use SCC's, making it unable to annotate pods running under normal admission control (i.e. in namespaces without `openshift.io/run-level` annotation). Annotating pods is essential for Kuryr to work.

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

How reproducible:
Always

Steps to Reproduce:
1. Install OCP 4.2 on OpenStack with Kuryr
2. Create a regular namespace
3. Create pod in that namespace

Actual results:
Pod hangs in ContainerCreating state

Expected results:
Pod gets into Running state.

Additional info:

Comment 2 Itzik Brown 2019-10-06 08:33:00 UTC
4.2.0-0.nightly-2019-10-02-122541

Comment 3 errata-xmlrpc 2019-10-16 06:41:28 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