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

Bug 1983109

Summary:	Pods stuck in Pending state with event failed to configure pod interface: timed out waiting for pod flows for pod
Product:	OpenShift Container Platform	Reporter:	aharchin
Component:	Networking	Assignee:	Tim Rozet <trozet>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	astoycos, bbennett, dgautam, trozet, wwinter
Version:	4.6
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-22 16:09:02 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:

Comment 1 aharchin 2021-07-19 13:35:52 UTC

Hi Team,

Any update on this?

Regards,
Akhil Harchinder
Red Hat

Comment 2 Tim Rozet 2021-07-20 19:44:51 UTC

This looks the same as https://bugzilla.redhat.com/show_bug.cgi?id=1952819 to me. We can see in ovn-controller there was no binding for alertmanager-main-1. That indicates to me that the entry is not in the db. Can you confirm? Either attach the db or exec into the nbdb:
oc exec -n openshift-ovn-kubernetes ovnkube-master-4tljb -c nbdb ovn-nbctl --no-leader-only list logical_switch_port openshift-monitoring_alertmanager-main-1

If there is no row (entry), then restart the *active* ovnkube-master pod. Check and see if this instance becomes active again, if not you may need to restart other ovnkube-masters. This should effectively re-initialize the cache with the logical port missing and correctly create the missing port in the db. If this works then it is definitely 1952819.

Thanks.