fix(vm): create pvc disk.img for hotplug volumes on migration target#2367
Merged
yaroslavborbat merged 1 commit intoMay 20, 2026
Merged
Conversation
e3934a7 to
66878da
Compare
Signed-off-by: Yaroslav Borbat <yaroslav.borbat@flant.com>
66878da to
1469c46
Compare
danilrwx
approved these changes
May 20, 2026
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
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
Bump KubeVirt version in Deckhouse Virtualization to include our upstream fork fix for migration target hotplug volume handling.
The fix enables
disk.imgcreation for filesystem hotplug PVCs on migration target before mount.Why do we need it, and what problem does it solve?
Live migration of VMs with filesystem hotplug PVCs could fail on target with:
.../disk.img: no such file or directory.Reason: migration target path did not create
disk.imgwhen needed.After this bump, migration target uses the fixed behavior and migration succeeds for this case.
What is the expected result?
disk.imgmount errors appear in targetvirt-handlerlogs.Checklist
Changelog entries