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

Bug 1928839

Summary: [sig-auth][Feature:SCC][Early] should not have pod creation failures during install test is flaky
Product: OpenShift Container Platform Reporter: Jan Safranek <jsafrane>
Component: apiserver-authAssignee: David Eads <deads>
Status: CLOSED DUPLICATE QA Contact: liyao
Severity: medium Docs Contact:
Priority: low    
Version: 4.6CC: adam.kaplan, aos-bugs, jhrozek, lszaszki, mfojtik, surbania, vpickard, wking, wlewis
Target Milestone: ---Flags: mfojtik: needinfo?
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: tag-ci
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1887850 Environment:
[sig-auth][Feature:SCC][Early] should not have pod creation failures during install
Last Closed: 2021-08-16 12:55:08 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: 1887850, 1913069    
Bug Blocks:    

Comment 1 Jan Safranek 2021-02-15 16:01:37 UTC 
4.6 flakes: https://search.ci.openshift.org/?search=%5C%5Bsig-auth%5C%5D%5C%5BFeature%3ASCC%5C%5D%5C%5BEarly%5C%5D+should+not+have+pod+creation+failures+during+install&maxAge=48h&context=1&type=bug%2Bjunit&name=4.6&maxMatches=5&maxBytes=20971520&groupBy=job

Example: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-gcp/1360104573171142656

From the other bugs, it seems that both https://github.com/openshift/kubernetes/pull/391 and https://github.com/openshift/origin/pull/25628 is needed.
Comment 2 W. Trevor King 2021-02-19 01:18:49 UTC 
[1] softens one test that was failing on this.  Once this issue is fixed, we should revert the softening.

[1]: https://github.com/openshift/origin/pull/25906
Comment 3 Adam Kaplan 2021-02-22 20:54:58 UTC 
This is flaky on 4.8 too, and code freeze for 4.7 has passed. Updated target version to 4.8.
Comment 7 Michal Fojtik 2021-03-25 19:50:51 UTC 
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Comment 9 Michal Fojtik 2021-07-09 16:45:44 UTC 
The LifecycleStale keyword was removed because the bug got commented on recently.
The bug assignee was notified.
Comment 10 Michal Fojtik 2021-08-08 16:53:19 UTC 
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Comment 11 Sergiusz Urbaniak 2021-08-09 14:40:15 UTC 
removing lifecyle stale tag, we're actively investigating
Comment 12 Sergiusz Urbaniak 2021-08-16 12:55:08 UTC 
This seems to have the same underlying issue as #1970331, hence marking as a duplicate.

*** This bug has been marked as a duplicate of bug 1970331 ***