-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Rejected
-
CORENET Sprint 270
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Most recent 4.19 payload failed in aggregated-aws-ovn-upgrade-4.19-micro-fips with three failures ofÂ
[bz-networking][invariant] alert/OVNKubernetesResourceRetryFailure should not be at or above info
search.ci has a number of instances of this popping up, against various 4.19/4.20 jobs - not sure they're all related, but at least the three instances aggregated in the job above have interval charts that all look about the same; possibly this is just the only time it happened often enough to show up on a payload, but I suspect it will show up in component readiness soon.
I saw no obviously-related changes in recent PRs.
Affected Platforms:
Most hits from search.ci are on AWS, but I see a few on vsphere and libvirt too.
It is an
- internal CI failure
- duplicates
-
OCPBUGS-55824 OVN-Kubernetes flows caused OVS CPU Regression in 4.19.0 RC - component readiness
-
- Verified
-
- links to