Skip to content

Conversation

hardcoretime
Copy link
Contributor

@hardcoretime hardcoretime commented Sep 6, 2025

Description

The new migration test case has been added.

Why do we need it, and what problem does it solve?

What is the expected result?

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.

Changelog entries

section: api
type: chore
summary: "The new migration test case has been added."
impact_level: low

@hardcoretime hardcoretime requested a review from Isteb4k September 6, 2025 01:38
@hardcoretime hardcoretime added this to the v1.0.0 milestone Sep 6, 2025
@hardcoretime hardcoretime force-pushed the test/vm/check-tcp-connection-when-vm-migrate branch from e375c86 to 657fa7e Compare September 6, 2025 01:47
@hardcoretime hardcoretime force-pushed the test/vm/check-tcp-connection-when-vm-migrate branch from 657fa7e to 2dcdb22 Compare September 6, 2025 10:59
@nevermarine nevermarine modified the milestones: v1.0.0, v1.1.0 Sep 11, 2025
@Isteb4k Isteb4k force-pushed the test/vm/check-tcp-connection-when-vm-migrate branch from f356aa7 to 2dcdb22 Compare September 16, 2025 07:26
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.

4 participants