gh: conn-disrupt: fix XFRM error checks#42724
Merged
julianwiedmann merged 1 commit intomainfrom Nov 13, 2025
Merged
Conversation
Member
Author
|
/ci-ipsec-e2e |
Member
Author
|
/ci-e2e-upgrade |
Member
Author
|
Going back through old CI, this seems to affect
|
Member
Author
|
Oh nice, hit one error straight away:
|
8a63277 to
f3622d0
Compare
Member
Author
|
/test |
XFRM error checking is supposed to occur before/after a conn-disrupt test. During the test-setup step we collect the initial XFRM errors, and the test-check step is meant to compare the new error count against the previously collected error count. But this requires that we actually run the `no-ipsec-xfrm-error` test during conn-disrupt's test-check step. Opt-out the ipsec-e2e workflow for now until the observed `XfrmOutPolBlock` errors are addressed. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
f3622d0 to
96b05d6
Compare
Member
Author
|
/test |
pchaigno
approved these changes
Nov 13, 2025
This was referenced Nov 13, 2025
pchaigno
reviewed
Nov 13, 2025
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
XFRM error checking is supposed to occur before/after a conn-disrupt test. During the test-setup step we collect the initial XFRM errors, and the test-check step is meant to compare the new error count against the previously collected error count.
But this requires that we actually run the
no-ipsec-xfrm-errortest during conn-disrupt's test-check step.Opt-out the ipsec-e2e workflow for now until the observed
XfrmOutPolBlockerrors are addressed.