Bug 2053704

Summary:	failed to get pod annotation: timed out waiting for annotations
Product:	OpenShift Container Platform	Reporter:	Anand T N <atn>
Component:	Networking	Assignee:	jamo luhrsen <jluhrsen>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	urgent
Priority:	high	CC:	anbhat, apizarro, dcbw, dceara, dhellard, emahoney, evadla, ffernand, jluhrsen, johlong, openshift-bugs-escalate, trozet
Version:	4.8	Flags:	jluhrsen: needinfo- jluhrsen: needinfo-
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-29 20:41:51 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 Anand T N 2022-02-11 19:27:22 UTC

Description of problem:

- ovn-kubernetes multus-cni-network problem due to this failure to spin up any pod in the environment

pods are getting stuck in "Init:0/2" state and run into below error:

error adding pod to CNI network "multus-cni-network": error adding container to network "ovn-kubernetes": still waiting for readinessindicatorfile @ /var/run/multus/cni/net.d/10-ovn-kubernetes.conf. pollimmediate error: timed out waiting for the condition



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

Comment 3 Dwayne 2022-02-11 20:59:26 UTC

Set Customer Escalation flag = Yes, per RME EN-48246

Impact per customer, "Error causes outage. Impacting our ability to deploy. Need a bug fix or eta on when bug fix will be available."

Comment 27 Tim Rozet 2022-03-29 20:41:51 UTC


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