Skip to content

CORENET-6746: Allow EgressIP NoMatchingNodeFound events to repeat pathologically #31614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pperiyasamy wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −0
Open

CORENET-6746: Allow EgressIP NoMatchingNodeFound events to repeat pathologically #31614

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions pkg/monitortestlibrary/pathologicaleventlibrary/duplicated_event_patterns.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -577,6 +577,15 @@ func NewUniversalPathologicalEventMatchers(kubeConfig *rest.Config, finalInterva
jira: "https://redhat.atlassian.net/browse/OCPBUGS-84917",
})

// EgressIP e2e tests create EgressIP resources before labeling nodes with
// k8s.ovn.org/egress-assignable, so NoMatchingNodeFound events fire repeatedly
// until the label is applied. This is expected test behavior, not a real problem.
registry.AddPathologicalEventMatcherOrDie(&SimplePathologicalEventMatcher{
name: "EgressIPNoMatchingNodeFound",
messageReasonRegex: regexp.MustCompile(`^NoMatchingNodeFound$`),
messageHumanRegex: regexp.MustCompile(`no assignable nodes for EgressIP`),
})

return registry
}

Expand Down