doc: vm random migration issue #950
Conversation
github-actions
bot
requested review from
akashraj4261,
dariavladykina and
jillian-maroket
There was a problem hiding this comment.
Pull request overview
This PR adds documentation for a known issue where VMs cannot be live migrated to a specific target node after upgrading from Harvester v1.5.x to v1.6.x. The documentation explains that VMs are migrated to a random node instead and provides a workaround by restarting the VM.
- Adds a new section (### 7) documenting the VM migration issue after upgrade
- Updates subsequent section numbering from 7 to 8 for VLAN behavior changes
- Includes reference to the related GitHub issue #9739
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| versioned_docs/version-v1.7/upgrade/v1-5-x-to-v1-6-x.md | Adds VM migration issue documentation and renumbers subsequent section |
| versioned_docs/version-v1.6/upgrade/v1-5-x-to-v1-6-x.md | Adds VM migration issue documentation and renumbers subsequent section |
| docs/upgrade/v1-5-x-to-v1-6-x.md | Adds VM migration issue documentation, renumbers subsequent section, and adds trailing newline |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Jack Yu <jack.yu@suse.com>
|
There was a problem hiding this comment.
Can we also update the 1.6 live migration document at https://docs.harvesterhci.io/v1.6/vm/live-migration/#starting-a-migration, under the existing 'note' section with something like:
Due to a limitation in the workload rollout strategy implementation, virtual machines that are pending restart may get live-migrated to a random node, instead of the specified target node. The virtual machines must be restarted for all subsequent targeted live migration to work.
docs/upgrade/v1-5-x-to-v1-6-x.md
Outdated
| ### 7. Change in Default VLAN Behavior for Secondary Pod Interfaces | ||
| ### 7. Virtual Machine Cannot Be Live Migrated to the Target Node | ||
| After upgrading Harvester to v1.6.x, virtual machines from v1.5.x cannot be live migrated to a user-specified target node. Instead, the virtual machines are migrated to a random node. This issue occurs because of the `RestartRequired` condition, which indicates that the virtual machines require a restart. |
There was a problem hiding this comment.
| After upgrading Harvester to v1.6.x, virtual machines from v1.5.x cannot be live migrated to a user-specified target node. Instead, the virtual machines are migrated to a random node. This issue occurs because of the `RestartRequired` condition, which indicates that the virtual machines require a restart. | |
| After upgrading Harvester to v1.6.x, KubeVirt may report that some virtual machines are pending restart. These virtual machines cannot be live migrated to a user-specified target node from the UI, until they are restarted. Once restarted, subsequent node-specific live migrations will work. |
Here and elsewhere - thanks.
There was a problem hiding this comment.
Added. I changed some description and made it more synced between them.
Signed-off-by: Jack Yu <jack.yu@suse.com>
| After upgrading Harvester to v1.6.x, KubeVirt may report that some virtual machines are pending restart. These virtual machines cannot be live migrated to a user-specified target node from the UI, until they are restarted. Once restarted, subsequent node-specific live migrations will work. | ||
| The workaround is to restart the virtual machine. |
There was a problem hiding this comment.
| After upgrading Harvester to v1.6.x, KubeVirt may report that some virtual machines are pending restart. These virtual machines cannot be live migrated to a user-specified target node from the UI, until they are restarted. Once restarted, subsequent node-specific live migrations will work. | |
| The workaround is to restart the virtual machine. | |
| Following an upgrade to v1.6.x, some virtual machines may remain in a _pending restart_ state. These virtual machines cannot be live migrated to the specified target node until they are restarted. | |
| The workaround is to restart the virtual machines. Once restarted, subsequent node-specific live migrations will work. |
3 participants
harvester/harvester#9739