Skip to content

Conversation

@mmartin24
Copy link
Collaborator

This test has failed today because it glitched somehow while attempting to click on hamburger menu to access cluster.
The initial idea to mitigate (not fix) this was to increase sleep time.

However, before doing this I noticed after setting cluster options for Scheduling and clicking save there were unnecessary steps to reach the cluster and check the status

Although the steps were not a problem themselves, instead of adding waits for mitigation I opted for removing this part as the user is immediately taken into cluster page right after saving config.

CI green: https://github.com/rancher/fleet-e2e/actions/runs/19711339402/job/56472578546

Copy link
Collaborator

@sbulage sbulage left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@mmartin24 mmartin24 merged commit 44d946a into main Nov 27, 2025
12 checks passed
@mmartin24 mmartin24 deleted the fleetqa/addressing-flaky-fleet200 branch November 27, 2025 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants