# [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]
flake: pre-test environment had disruption and limited this test, suppressing failure: 1 pods failed before test on SCC errors

May 23 19:40:44.686 - 2834s E alert/Watchdog ns/openshift-monitoring ALERTS{alertname="Watchdog", alertstate="firing", namespace="openshift-monitoring", prometheus="openshift-monitoring/k8s", severity="none"}
May 23 19:40:47.465 E e2e-test/"[sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]" finishedStatus/Flaked
May 23 19:40:55.946 E ns/e2e-init-container-2000 pod/pod-init-9549b23a-884f-4f51-bd51-b2d6f03d606d node/ip-10-0-205-179.ec2.internal uid/f6bd2629-40a7-4268-b16d-155966fd42f7 container/init2 reason/ContainerExit code/1 cause/Error

# [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]
fail [github.com/openshift/origin/test/extended/util/client.go:334]: Unexpected error:

# [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]
flake: pre-test environment had disruption and limited this test, suppressing failure: 1 pods failed before test on SCC errors

May 23 13:04:58.218 - 2922s E alert/Watchdog ns/openshift-monitoring ALERTS{alertname="Watchdog", alertstate="firing", namespace="openshift-monitoring", prometheus="openshift-monitoring/k8s", severity="none"}
May 23 13:05:02.064 E e2e-test/"[sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]" finishedStatus/Flaked
May 23 13:05:14.773 E ns/e2e-container-runtime-5556 pod/terminate-cmd-rpa7ffa330a-339e-48b4-b225-92e7e8600a18 node/ci-op-zppmz5k3-7f65d-szcb2-worker-centralus3-pdnrt uid/bcf134fd-6c68-4295-9e2d-84a621d8b063 container/terminate-cmd-rpa reason/ContainerExit code/1 cause/Error

# [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]
flake: pre-test environment had disruption and limited this test, suppressing failure: 1 pods failed before test on SCC errors

May 23 08:18:21.045 - 3056s E alert/Watchdog ns/openshift-monitoring ALERTS{alertname="Watchdog", alertstate="firing", namespace="openshift-monitoring", prometheus="openshift-monitoring/k8s", severity="none"}
May 23 08:18:24.736 E e2e-test/"[sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]" finishedStatus/Flaked
May 23 08:18:38.191 E ns/e2e-init-container-8365 pod/pod-init-414f1abd-faf2-4a42-a968-672d4c7085a9 node/ci-op-0w9sl7sw-7f65d-6rw7v-worker-centralus3-mzcpf uid/346be90b-a107-4399-96bd-795214bb3862 container/init2 reason/ContainerExit code/1 cause/Error

# [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]
fail [github.com/openshift/origin/test/extended/util/client.go:384]: Unexpected error:

-failures-summary_20250523-071658.json]
response Body: {"ProwJobName":"periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-aws-sdn-upgrade-infra","ProwJobRunID":1925782255150567424,"Release":"4.12","CompareRelease":"4.12","Tests":[{"Name":"[sig-scheduling][Early] The openshift-image-registry pods [apigroup:imageregistry.operator.openshift.io] should be scheduled on different nodes [Suite:openshift/conformance/parallel]","TestID":0,"Risk":{"Level":{"Name":"Low","Level":1},"Reasons":["This test has passed 66.67% of 3 runs on jobs [periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-aws-sdn-upgrade-infra periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-aws-upgrade-infra] in the last 14 days."],"CurrentRuns":3,"CurrentPasses":2,"CurrentPassPercentage":66.66666666666667},"OpenBugs":[]},{"Name":"[sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]","TestID":0,"Risk":{"Level":{"Name":"Medium","Level":50},"Reasons":["This test has passed 80.00% of 5 runs on jobs [periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-aws-sdn-upgrade-infra periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-aws-upgrade-infra] in the last 14 days."],"CurrentRuns":5,"CurrentPasses":4,"CurrentPassPercentage":80},"OpenBugs":[]}],"OverallRisk":{"Level":{"Name":"Medium","Level":50},"Reasons":["Maximum failed test risk: Medium"],"JobRunTestCount":520,"JobRunTestFailures":2,"NeverStableJob":false,"HistoricalRunTestCount":520},"OpenBugs":[]}

-failures-summary_20250523-071658.json]
response Body: {"ProwJobName":"periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-aws-sdn-upgrade-infra","ProwJobRunID":1925782255150567424,"Release":"4.12","CompareRelease":"4.12","Tests":[{"Name":"[sig-scheduling][Early] The openshift-image-registry pods [apigroup:imageregistry.operator.openshift.io] should be scheduled on different nodes [Suite:openshift/conformance/parallel]","TestID":0,"Risk":{"Level":{"Name":"Low","Level":1},"Reasons":["This test has passed 66.67% of 3 runs on jobs [periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-aws-sdn-upgrade-infra periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-aws-upgrade-infra] in the last 14 days."],"CurrentRuns":3,"CurrentPasses":2,"CurrentPassPercentage":66.66666666666667},"OpenBugs":[]},{"Name":"[sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]","TestID":0,"Risk":{"Level":{"Name":"Medium","Level":50},"Reasons":["This test has passed 80.00% of 5 runs on jobs [periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-aws-sdn-upgrade-infra periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-aws-upgrade-infra] in the last 14 days."],"CurrentRuns":5,"CurrentPasses":4,"CurrentPassPercentage":80},"OpenBugs":[]}],"OverallRisk":{"Level":{"Name":"Medium","Level":50},"Reasons":["Maximum failed test risk: Medium"],"JobRunTestCount":520,"JobRunTestFailures":2,"NeverStableJob":false,"HistoricalRunTestCount":520},"OpenBugs":[]}

# [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]
fail [github.com/openshift/origin/test/extended/authorization/scc.go:69]: 2 pods failed before test on SCC errors

May 23 07:16:59.320 - 5s    E e2e-test/"[sig-scheduling][Early] The openshift-image-registry pods [apigroup:imageregistry.operator.openshift.io] should be scheduled on different nodes [Suite:openshift/conformance/parallel]" e2e test finished As "Failed"
May 23 07:17:04.790 - 3s    E e2e-test/"[sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]" e2e test finished As "Failed"
May 23 07:17:04.889 E e2e-test/"[sig-scheduling][Early] The openshift-image-registry pods [apigroup:imageregistry.operator.openshift.io] should be scheduled on different nodes [Suite:openshift/conformance/parallel]" finishedStatus/Failed
May 23 07:17:08.696 E e2e-test/"[sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]" finishedStatus/Failed