Skip to content
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.

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

[e2e] Test have been failing for a long time #242

Closed
richardcase opened this issue Jan 18, 2024 · 10 comments · Fixed by #260
Closed

[e2e] Test have been failing for a long time #242

richardcase opened this issue Jan 18, 2024 · 10 comments · Fixed by #260
Assignees
Labels
area/testing Indicates an issue related to test help wanted Extra attention is needed kind/bug Something isn't working priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@richardcase
Copy link
Contributor

What happened:
Our nightly e2e test have been failing for a long time now.

What did you expect to happen:
The tests to pass consistently

How to reproduce it:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • rke provider version:
  • OS (e.g. from /etc/os-release):
@richardcase richardcase added help wanted Extra attention is needed area/testing Indicates an issue related to test kind/bug Something isn't working priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 18, 2024
@furkatgofurov7 furkatgofurov7 self-assigned this Jan 25, 2024
@Danil-Grigorev
Copy link
Contributor

Danil-Grigorev commented Feb 13, 2024

@furkatgofurov7 To fix this we need to fix #263. I propose to do this in a separate PR and merge #260 as is, as it resolves contract issue.

@Danil-Grigorev
Copy link
Contributor

Also, kubernetes-sigs/cluster-api#9952 seems to be required here too.

@Danil-Grigorev
Copy link
Contributor

Danil-Grigorev commented Feb 19, 2024

@richardcase I think this was closed by mistake. e2e tests are not passing with this merged change alone for me.

@richardcase
Copy link
Contributor Author

They passed for me this morning

@Danil-Grigorev
Copy link
Contributor

@furkatgofurov7 You mentioned there is an issue with the e2e tests, later in the run. Can you give more details? I’ll retry on my side as well. In my setup I was hitting originally this issue: #263

@richardcase
Copy link
Contributor Author

richardcase commented Feb 19, 2024

Maybe this is now hinting an environmental factors. I will run it in different environments to check.

I also created #267 so we can run the e2e via self hosted runners, to test.

@furkatgofurov7
Copy link
Contributor

@furkatgofurov7 You mentioned there is an issue with the e2e tests, later in the run. Can you give more details? I’ll retry on my side as well. In my setup I was hitting originally this issue: #263

It was running in my fork, re-running it again to test the latest changes https://github.com/furkatgofurov7/cluster-api-provider-rke2/actions/runs/7958544104/job/21723628664

@Danil-Grigorev
Copy link
Contributor

I see the job is passing green. It looks like it is environment specific in some way: https://github.com/rancher-sandbox/cluster-api-provider-rke2/actions/runs/7958280349

@furkatgofurov7
Copy link
Contributor

furkatgofurov7 commented Feb 19, 2024

@furkatgofurov7 You mentioned there is an issue with the e2e tests, later in the run. Can you give more details? I’ll retry on my side as well. In my setup I was hitting originally this issue: #263

It was running in my fork, re-running it again to test the latest changes https://github.com/furkatgofurov7/cluster-api-provider-rke2/actions/runs/7958544104/job/21723628664

Passed in my fork as well: https://github.com/furkatgofurov7/cluster-api-provider-rke2/actions/runs/7958544104

@Danil-Grigorev
Copy link
Contributor

Yes, it passed for me as well. There was a change I overlooked - changed number of nodes from 1 to 3. This corresponds with a workaround for the bug intended to be fixed #263 and thus e2e does not hit the problem anymore.

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 help wanted Extra attention is needed kind/bug Something isn't working priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Development

Successfully merging a pull request may close this issue.

3 participants