Skip to content

fix(vmrestore): restore AlwaysOn vm with forced mode #1294

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Aug 1, 2025
Merged

fix(vmrestore): restore AlwaysOn vm with forced mode #1294

merged 3 commits into from
Aug 1, 2025

Conversation

hardcoretime
Copy link
Contributor

@hardcoretime hardcoretime commented Jul 31, 2025 •
edited
Loading

Description

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

A virtual machine with the AlwaysOn run policy cannot be stopped during the restoring process using forced mode.

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: fix
summary: "A virtual machine with the `AlwaysOn` run policy can be restored with the `forced` mode."

@hardcoretime hardcoretime added this to the v0.24.0 milestone Jul 31, 2025
@hardcoretime hardcoretime force-pushed the fix/vmrestore/restore-alwayson-vm-with-forced-mode branch from 35b216b to a488300 Compare July 31, 2025 09:31
@hardcoretime hardcoretime marked this pull request as ready for review July 31, 2025 14:14
danilrwx
danilrwx previously approved these changes Jul 31, 2025
View reviewed changes
@hardcoretime hardcoretime modified the milestones: v0.24.0, v0.23.1 Aug 1, 2025
@hardcoretime hardcoretime merged commit d125f75 into main Aug 1, 2025
27 of 29 checks passed
@hardcoretime hardcoretime deleted the fix/vmrestore/restore-alwayson-vm-with-forced-mode branch August 1, 2025 10:14
@deckhouse-BOaTswain deckhouse-BOaTswain mentioned this pull request Aug 1, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@danilrwx danilrwx danilrwx approved these changes

@Isteb4k Isteb4k Awaiting requested review from Isteb4k Isteb4k is a code owner

@yaroslavborbat yaroslavborbat Awaiting requested review from yaroslavborbat yaroslavborbat is a code owner

Assignees

@hardcoretime hardcoretime

Labels
None yet
Projects
None yet
Milestone
v0.23.1
Development

Successfully merging this pull request may close these issues.
2 participants
@hardcoretime @danilrwx