Skip to content

test(test): add iperf migration continuity checks to release e2e#2617

Merged
hayer969 merged 1 commit into
mainfrom
feat/test/release-iperf-migration-checks
Jul 9, 2026
Merged

test(test): add iperf migration continuity checks to release e2e#2617
hayer969 merged 1 commit into
mainfrom
feat/test/release-iperf-migration-checks

Conversation

@hayer969

@hayer969 hayer969 commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

The release test confirmed that iperf kept running across the upgrade, the added checks make the test actually prove the TCP session was not interrupted by the migration.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.
section: test
type: feature
summary: "The release upgrade e2e test now verifies that a long-running TCP session survives virtual machine live migration during the module upgrade."
impact_level: low

@hayer969 hayer969 requested a review from Isteb4k as a code owner July 8, 2026 18:05
@hayer969 hayer969 requested review from universal-itengineer and removed request for Isteb4k July 8, 2026 18:06
@hayer969 hayer969 added this to the v1.10.0 milestone Jul 8, 2026
Add validation to getIPerfClientReport verifying that the iperf client session spans the virtual machine migration: start time before migration start, end time after migration end, and no more than one zero-byte interval during the process.

Signed-off-by: Dmitry Prytkov <dmitry.prytkov@flant.com>
@hayer969 hayer969 force-pushed the feat/test/release-iperf-migration-checks branch from a6a66ca to 5b8aa84 Compare July 8, 2026 18:13
@hayer969 hayer969 merged commit 7600bd0 into main Jul 9, 2026
50 of 54 checks passed
@hayer969 hayer969 deleted the feat/test/release-iperf-migration-checks branch July 9, 2026 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants