Bug 1983109 - Pods stuck in Pending state with event failed to configure pod interface: timed out waiting for pod flows for pod
Summary: Pods stuck in Pending state with event failed to configure pod interface: tim...
Status: CLOSED DUPLICATE of bug 1952819
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Tim Rozet
QA Contact: Anurag saxena
Depends On:
TreeView+ depends on / blocked
Reported: 2021-07-16 14:28 UTC by aharchin
Modified: 2021-07-22 16:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-22 16:09:02 UTC
Target Upstream Version:

Attachments (Terms of Use)

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

Any update on this?

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.


Note You need to log in before you can comment on or make changes to this bug.