fix(vmop): correct reconcile deleted by strict restoring resources (#1878) #1905
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
diafour
requested review from
danilrwx and
eofff
and removed request for
Isteb4k and
yaroslavborbat
universal-itengineer
force-pushed
the
release-1.4
branch
from
2dfb0ed to
ad63eeb
Compare
diafour
force-pushed
the
fix/api/backport-pr1878-vmop-restore-stuck-in-progress
branch
from
4ba86e7 to
410dc3d
Compare
danilrwx
approved these changes
Jan 23, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Backport of #1878 into release 1.4
Why do we need it, and what problem does it solve?
This PR fix situations when VMOP Restore may stuck forever in the InProgress state waiting for VirtualDisk restoration.
What is the expected result?
VMOP Restore finishes successfully and not stuck in the InProgress state.
Checklist
Changelog entries