Which jobs are flaking?
pull-e2e-cluster-network-addons-operator-multus-functests
Detected in PR #2830, commit 60f29e2.
Which tests are flaking?
automation/check-patch.e2e-multus-functests.sh (script sourcing phase)
Since when has it been flaking?
2026-06-23
Reason for failure (if possible)
ERROR_SUMMARY: Bash syntax error in conditional expression due to unescaped closing parenthesis in regex character class (already fixed in subsequent commit)
ROOT_CAUSE: This CI run is testing an older commit (60f29e2) that contained a bash syntax error with an unescaped closing parenthesis in a regex pattern [^)]. The current HEAD commit (49e9d14) has already fixed this by changing the pattern to [^\)], properly escaping the closing paren.
EVIDENCE:
hack/components/yaml-utils.sh: line 39: syntax error in conditional expression: unexpected token `)'
+ EXIT_VALUE=2
RECOMMENDATION: This is a stale test run on an old commit. The issue has already been resolved in commit 49e9d14. The CI system will automatically run tests on the latest commit which contains the fix. No action needed - wait for the CI to test the current HEAD.
Anything else we need to know?
Automatically created by oompa.
Which jobs are flaking?
pull-e2e-cluster-network-addons-operator-multus-functests
Detected in PR #2830, commit 60f29e2.
Which tests are flaking?
automation/check-patch.e2e-multus-functests.sh (script sourcing phase)
Since when has it been flaking?
2026-06-23
Reason for failure (if possible)
ERROR_SUMMARY: Bash syntax error in conditional expression due to unescaped closing parenthesis in regex character class (already fixed in subsequent commit)
ROOT_CAUSE: This CI run is testing an older commit (60f29e2) that contained a bash syntax error with an unescaped closing parenthesis in a regex pattern
[^)]. The current HEAD commit (49e9d14) has already fixed this by changing the pattern to[^\)], properly escaping the closing paren.EVIDENCE:
RECOMMENDATION: This is a stale test run on an old commit. The issue has already been resolved in commit 49e9d14. The CI system will automatically run tests on the latest commit which contains the fix. No action needed - wait for the CI to test the current HEAD.
Anything else we need to know?
Automatically created by oompa.