Bug 2066949

Summary: Something in ovnkube-master causes CNI requests to fail with "timed out waiting for annotations"
Product: OpenShift Container Platform Reporter: Dan Small <dansmall>
Component: NetworkingAssignee: Surya Seetharaman <surya>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: bhershbe, surya
Version: 4.7Keywords: Reopened
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: 2022-03-30 23:20:44 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:

Description Dan Small 2022-03-22 20:03:21 UTC
Description of problem:

Deploying application pods, the pods got into crashloop with error (simplified): Failed to create pod sandbox CNI request failed with status 400: timed out waiting for annotations

Version-Release number of selected component (if applicable):
4.7.37

How reproducible:
Have been able to reproduce by redeploying their application


Additional info:
See next post for more details

Comment 4 Surya Seetharaman 2022-03-25 19:20:59 UTC
Checked the mustgather.

The pod was created around 14:00UTC and at that time master is simply sitting, no add logical port events are being processed. This is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2022049

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