fix(vm): preserve no bootable device error after migration#2463
Merged
Conversation
eofff
force-pushed
the
fix/vm/not-clear-boot-failed-when-migration
branch
from
4049d55 to
c7fbf6f
Compare
eofff
force-pushed
the
fix/vm/not-clear-boot-failed-when-migration
branch
from
ec1cb6b to
fe9cded
Compare
diafour
approved these changes
Jun 10, 2026
Contributor
Author
|
/backport 1.9 |
Contributor
|
Cherry pick PR 2468 to the branch release-1.9 successful! |
ArtemFedorov-Flant
pushed a commit
that referenced
this pull request
Jun 10, 2026
Signed-off-by: Valeriy Khorunzhin <valeriy.khorunzhin@flant.com>
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
3 participants
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 the
3p-kubevirtcomponent fromv1.6.2-v12n.42tov1.6.2-v12n.43.The updated KubeVirt artifact includes a fix that keeps the VM boot failure state when a VM with
No bootable device.is migrated.Why do we need it, and what problem does it solve?
A VM that failed to boot with
No bootable device.could lose that error state during migration. As a result, the VM status no longer reflected the real boot failure after the migration flow touched the VMI state.This change preserves the boot failure information across migration, so users and controllers continue to see the actual VM problem instead of a cleared status.
What is the expected result?
A VM that reaches the
No bootable device.boot failure state keeps this error during and after migration.To verify the fix, reproduce a VM boot failure with no bootable device, migrate the VM, and check that the VM status still reports the boot failure after migration completes.
Checklist