Repository navigation
docs(virtual-machine): correct persistent EFI migration documentation - #4494
Conversation
Assisted-by: LLM Signed-off-by: frolov.so <[email protected]>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: cozystack/cozystack/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (5)
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe ChangesEFI persistence descriptions
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other · Severity of issue fixed: Low Merge Risk: ⚪ Minimal · up to These documentation updates remove a blanket migration warning that repository documentation shows is outdated for the default replicated RWO filesystem backend. No actionable merge risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Aleksei Sviridkin (lexfrei)
left a comment
There was a problem hiding this comment.
∆Sergey∆ (@opsmon) LGTM — the removed sentence is wrong for the KubeVirt version this repo ships, and all five files match what the generator produces.
The chart only passes the value through. templates/vm.yaml:76 sets bootloader.efi.persistent from efiPersistent, and nothing else in the chart reads it. So the behaviour is KubeVirt's, and the pin is v1.9.0 (packages/system/kubevirt-operator/Makefile).
At v1.9.0 an RWO state PVC does not block live migration. CreatePVCForMigrationTarget in pkg/storage/backend-storage/backend-storage.go creates a new PVC on the target unless the source is RWX, and MigrationHandoff switches to it after the migration. The state PVC is also not in vmi.spec.volumes, so the RWX check in checkVolumesForMigration (pkg/virt-handler/vm.go) does not see it.
I ran make generate in packages/apps/vm-instance on this head and the tree stayed clean. helm unittest passes 59/59, and the old sentence is not left anywhere else in the repo.
What this PR does
Removes the outdated warning that persistent EFI state on default RWO storage makes a virtual machine node-pinned and prevents live migration. The warning no longer reflects the supported migration behavior and could discourage users from persisting Secure Boot keys.
This is a documentation-only change. The chart documentation, JSON schema, generated API comment, and ApplicationDefinition schema were regenerated without changing defaults, validation, or runtime behavior.
Fixes #4420
Validation
make -C packages/apps/vm-instance generatemake generatemake manifestsmake -C packages/apps/vm-instance test— 59 tests passedgit diff --checkScreenshots
N/A — documentation-only change.
Downstream repositories
Release note
Summary by CodeRabbit