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

Update e2e test to cover upgrade using desired nodes API #7679

Merged
merged 5 commits into from
Apr 2, 2024

Conversation

thbkrkr
Copy link
Contributor

@thbkrkr thbkrkr commented Mar 28, 2024

This updates TestVersionUpgradeSingleToLatest8x to use CPU requests and memory limits, so the desired nodes API is used during an upgrade.

Why update juste one test? I think there are two reasons why we don't set CPU resources by default for all tests:

  • we don't want to have flaky tests due to scheduling issue because of a lack of resources
  • we want to have fast tests with the max of CPU

Relates to #7664.

This first updates the test:

  • 6a67480 Update TestVersionUpgradeSingleToLatest8x with container resources

For testing, I reverted the fix to validate that this change in the test effectively fails without the #7663 fix:

  • a411102 Revert "Move desired nodes version gate in the client (7663)"

🟡 The build succeeded instead of failing? Normal, the test was not doing an ES upgrade to 8.13.0. Let's update the latest 8x. (Not smart, I could have simply set t=8.13.0 when triggering the test.)

🔴 Now the build failed and we have the expected error (elasticsearch client failed - [update_desired_nodes_request] failed to parse field [nodes] ) in the operator log in the diagnostics.

Reverting the revert to now validate that the fix already comitted fixes the new test:

  • 209d82c Revert "Revert "Move desired nodes version gate in the client (7663)"

🟢 The build succeeded.

@thbkrkr thbkrkr added the >test Related to unit/integration/e2e tests label Mar 28, 2024
@thbkrkr thbkrkr changed the title Update upgrade e2e test with resources Update e2e test to cover upgrade using desired nodes API Mar 28, 2024
@@ -18,7 +18,7 @@ const (
// LatestReleasedVersion7x is the latest released version for 7.x
LatestReleasedVersion7x = "7.17.8"
// LatestReleasedVersion8x is the latest release version for 8.x
LatestReleasedVersion8x = "8.12.1"
LatestReleasedVersion8x = "8.13.0"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same change in #7661.

@thbkrkr thbkrkr marked this pull request as ready for review March 29, 2024 09:44
@@ -182,13 +185,22 @@ func TestVersionUpgradeSingleToLatest8x(t *testing.T) {

test.SkipInvalidUpgrade(t, srcVersion, dstVersion)

resources := corev1.ResourceRequirements{
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe add a comment explaining your motivation for adding the explicit resource requirement.

@thbkrkr thbkrkr added the v2.13.0 label Apr 2, 2024
@thbkrkr thbkrkr merged commit aeeceac into main Apr 2, 2024
5 checks passed
@thbkrkr thbkrkr deleted the update-upgrade-e2e-test-with-resources branch April 2, 2024 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Related to unit/integration/e2e tests v2.13.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants