We shouldn't be logging or posting this event: E0418 23:11:24.064988 1 ovn.go:584] Failed to add pod 27f03550-node-density-20220418_node-density-25133, error: failed to ensurePod 27f03550-node-density-20220418/node-density-25133 since it is not yet scheduled I0418 23:11:24.065067 1 event.go:285] Event(v1.ObjectReference{Kind:"Pod", Namespace:"27f03550-node-density-20220418", Name:"node-density-25133", UID:"9713700c-f90c-436c-a010-4b23185e82b8", APIVersion:"v1", ResourceVersion:"454191", FieldPath:""}): type: 'Warning' reason: 'ErrorAddingLogicalPort' failed to ensurePod 27f03550-node-density-20220418/node-density-25133 since it is not yet scheduled If the pod isn't yet scheduled, we should just ignore the event and try again later.
Verified on 4.11.0-0.nightly-2022-05-11-054135 On 4.11.0-0.nightly-2022-05-11-054135: oc logs -n openshift-ovn-kubernetes -c ovnkube-master $(oc -n openshift-ovn-kubernetes get pod -l app=ovnkube-master -o jsonpath='{.items[0].metadata.name}' --field-selector=spec.nodeName=$(oc get -o jsonpath='{.metadata.annotations.control-plane\.alpha\.kubernetes\.io/leader}' -n openshift-ovn-kubernetes cm ovn-kubernetes-master | jq -r .holderIdentity)) | grep -c 'since it is not yet scheduled' 0 On 4.10 544 matches On 4.10 it looks like `openshift-marketplace` will frequently trigger the `since it is not yet scheduled`, no need to touch the cluster, e.g. error: failed to ensurePod openshift-marketplace/redhat-marketplace-sspk8 since it is not yet scheduled
*** Bug 2079380 has been marked as a duplicate of this bug. ***
I have hit the similar error on 4.10.0-0.nightly-2022-05-26-021757 [sninganu@sninganu ~]$ oc get events -n 002a6538-e5f9-4b67-9549-a940ce7a4d66 |grep -c -i Error 250 [sninganu@sninganu ~]$ oc get events -n 002a6538-e5f9-4b67-9549-a940ce7a4d66 |grep -i Error 68m Warning ErrorAddingLogicalPort pod/node-density-1 failed to ensurePod 002a6538-e5f9-4b67-9549-a940ce7a4d66/node-density-1 since it is not yet scheduled 68m Warning ErrorAddingLogicalPort pod/node-density-10 failed to ensurePod 002a6538-e5f9-4b67-9549-a940ce7a4d66/node-density-10 since it is not yet scheduled 68m Warning ErrorAddingLogicalPort pod/node-density-100 failed to ensurePod 002a6538-e5f9-4b67-9549-a940ce7a4d66/node-density-100 since it is not yet scheduled 68m Warning ErrorAddingLogicalPort pod/node-density-101 failed to ensurePod 002a6538-e5f9-4b67-9549-a940ce7a4d66/node-density-101 since it is not yet scheduled 68m Warning ErrorAddingLogicalPort pod/node-density-102 failed to ensurePod 002a6538-e5f9-4b67-9549-a940ce7a4d66/node-density-102 since it is not yet scheduled 68m Warning ErrorAddingLogicalPort pod/node-density-103 failed to ensurePod 002a6538-e5f9-4b67-9549-a940ce7a4d66/node-density-103 since it is not yet scheduled observed during the pod-density perf test. https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/scale-ci/job/e2e-benchmarking-multibranch-pipeline/job/kube-burner/412/consoleFull cluster https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/106377/
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 (Moderate: OpenShift Container Platform 4.11.3 packages and security update), 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/RHSA-2022:6287