Bug 2053704 - failed to get pod annotation: timed out waiting for annotations
Summary: failed to get pod annotation: timed out waiting for annotations
Keywords:
Status: CLOSED DUPLICATE of bug 2045577
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: ---
Assignee: jamo luhrsen
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-11 19:27 UTC by Anand T N
Modified: 2022-03-30 16:59 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-29 20:41:51 UTC
Target Upstream Version:
Embargoed:
jluhrsen: needinfo-
jluhrsen: needinfo-

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.