Skip to content

fix: ci flakes on cleanup#2602

Open
salasberryfin wants to merge 1 commit into
rancher:mainfrom
salasberryfin:fix_flaky_test_cleanup
Open

fix: ci flakes on cleanup#2602
salasberryfin wants to merge 1 commit into
rancher:mainfrom
salasberryfin:fix_flaky_test_cleanup

Conversation

@salasberryfin

@salasberryfin salasberryfin commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Trying to resolve the intermittent flakes of the CI tests because cleanup is failing on AfterEach.

After some investigation I suspect there may be some problem with write operations hitting the API directly and the cache not being updated accordingly.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@salasberryfin salasberryfin added kind/bug Something isn't working area/testing Indicates an issue related to test labels Jun 30, 2026
@salasberryfin
salasberryfin force-pushed the fix_flaky_test_cleanup branch from 6960edf to 920e714 Compare June 30, 2026 09:24
Signed-off-by: Carlos Salas <carlos.salas@suse.com>
@salasberryfin
salasberryfin force-pushed the fix_flaky_test_cleanup branch from 920e714 to 75d3b48 Compare June 30, 2026 09:55
@salasberryfin
salasberryfin marked this pull request as ready for review June 30, 2026 10:15
@salasberryfin
salasberryfin requested a review from a team as a code owner June 30, 2026 10:15

@anmazzotti anmazzotti left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that the entire logic of removing finalizers should be removed.
I feel like this is test cheating, and it will hide real failures where controllers are expected to remove their finalizers.

This logic seems to be used by the import controller only, which historically had some problems with finalizers, so could be some legacy test workaround.

So I don't think this PR is improving the situation, rather making it more elaborate.
I think it's fine as a mitigation, but I'd rather see a deeper investigation on why we are removing finalizers in the first place, instead of just deleting objects and wait for the controllers to reconcile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/testing Indicates an issue related to test kind/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants