Skip to content

[17.0-stable] evetest: upgrade a three-node EVE-k cluster - #6868

Merged
milan-zededa merged 1 commit into
lf-edge:17.0-stablefrom
eriknordmark:cluster-upgrade-test-17.0-stable
Oct 19, 2026
Merged

milan-zededa merged 1 commit into
lf-edge:17.0-stablefrom
eriknordmark:cluster-upgrade-test-17.0-stable

Conversation

@eriknordmark

Copy link
Copy Markdown
Contributor

Description

Backport of #6673 to 17.0-stable.

Adds TestThreeNodesUpgrade to TestUpgradeSuite: a three-node EVE-k cluster forms on an earlier EVE, runs a container app, and is upgraded one node at a time, bootstrap node last, with every node Ready and storage healthy after each step and the app still answering at the end.

Cherry-picked with -x from 850c08d. One adaptation: the PR hoists the suite's EVE-k baseline constant to package level so the new test can default to it. On this branch that constant is already 17.0.1-rc2 (the first 17.0 tag carrying #6404), not master's 0.0.0-master-66475696, so the branch's own value is the one hoisted. cluster_upgrade_test.go is identical to master's.

How to test and validate this PR

EVETEST_HYPERVISOR=kubevirt make evetest NAME=TestThreeNodesUpgrade
make evetest NAME=TestUpgradeSuite

It passes when every node-<name>-upgraded checkpoint is reached and the app answers after the last upgrade.

Changelog notes

None, test only.

PR Backports

  • 17.0-stable: this PR.
  • 16.0-stable: No, the evetest framework exists only on 17.0-stable.
  • 14.5-stable: No, the evetest framework exists only on 17.0-stable.
  • 13.4-stable: No, the evetest framework exists only on 17.0-stable.

Checklist

  • I've provided a proper description
  • I've added the proper documentation
  • I've tested my PR on amd64 device
  • I've tested my PR on arm64 device
  • I've written the test verification instructions
  • I've set the proper labels to this PR
  • I've checked the boxes above, or I've provided a good reason why I didn't
    check them.

🤖 Generated with Claude Code

Form a three-node cluster on an earlier EVE-k, deploy a container app,
and upgrade the nodes one at a time to the version under test,
bootstrap node last. After each upgrade a fresh cluster report must
show every node Ready, and at the end the app must still answer. The
test runs in TestUpgradeSuite and by default starts from the same
baseline as the suite's EVE-k upgrade variant, which on 17.0-stable is
17.0.1-rc2. The initial version and repo are parameters; the target
defaults to the checked-out HEAD.

Signed-off-by: eriknordmark <erik@zededa.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 850c08d)
@eriknordmark eriknordmark added the testing New test or test framework changes label Oct 19, 2026
@milan-zededa

Copy link
Copy Markdown
Contributor

No need to wait for eden, not relevant here.

@milan-zededa
milan-zededa merged commit 2ff7e38 into lf-edge:17.0-stable Oct 19, 2026
38 of 39 checks passed
@eriknordmark
eriknordmark deleted the cluster-upgrade-test-17.0-stable branch October 27, 2026 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing New test or test framework changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants