Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: VMO known issue update after engineering review #5461

Merged
merged 1 commit into from
Jan 17, 2025
Merged

docs: VMO known issue update after engineering review #5461

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/docs-content/release-notes/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ The following table lists all known issues that are currently active and affecti

| Description | Workaround | Publish Date | Product Component |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- |
| When using the [VM Migration Assistant](../vm-management/vm-migration-assistant/vm-migration-assistant.md) to migrate VMs to your Virtual Machine Orchestrator (VMO) cluster, migration plans can enter an **Unknown** state if you have selected to migrate more VMs than the **Max concurrent virtual machine migrations** setting allows. | Review the [Virtual Machine Orchestrator (VMO) Troubleshooting](../troubleshooting/vmo-issues.md#scenario---virtual-machine-vm-migration-plans-in-unknown-state) section for workarounds. | January 18, 2025 | Virtual Machine Orchestrator |
| When using the [VM Migration Assistant](../vm-management/vm-migration-assistant/vm-migration-assistant.md) to migrate VMs to your VMO cluster, migration plans can enter an **Unknown** state if more VMs are selected for migration than the **Max concurrent virtual machine migrations** setting allows. | Review the [Virtual Machine Orchestrator (VMO) Troubleshooting](../troubleshooting/vmo-issues.md#scenario---virtual-machine-vm-migration-plans-in-unknown-state) section for workarounds. | January 18, 2025 | Virtual Machine Orchestrator |
| Palette upgrades on K3s virtual clusters may be blocked if the cluster does not have enough resources to accommodate additional pods. Ensure that your cluster has 1 CPU, 1 GiB of memory, and 1 GiB storage of free resources before commencing an upgrade. You may increase the virtual cluster's resource quotas or disable them. | Refer to the [Adjust Virtual Clusters Limits](../troubleshooting/palette-dev-engine.md#scenario---adjust-virtual-clusters-limits-before-palette-upgrades) guide for workaround steps. | January 18, 2025 | Virtual Clusters |
| If you have manually configured the metrics server in your Edge airgap cluster using a manifest, upgrading to 4.5.15 may cause an additional metrics server pod to be created in your cluster. | Remove the manifest layer that adds the manifest server from your cluster profile and apply the update on your cluster. | December 15, 2024 | Edge |
| When deploying an Edge cluster using content bundles built from cluster profiles with PXK-E as the Kubernetes layer, some images in the Kubernetes layer fail to load into containerd. This issue occurs due to image signature problems, resulting in deployment failure. | Remove the `packs.content.images` from the Kubernetes layer in the pack configuration before building the content bundle. These components are already included in the provider image and do not need to be included in the content bundle. | December 13, 2024 | Edge |
Expand Down
14 changes: 8 additions & 6 deletions docs/docs-content/troubleshooting/vmo-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,15 @@ The following are common scenarios that you may encounter when using Virtual Mac
## Scenario - Virtual Machine (VM) Migration Plans in Unknown State

When using the [VM Migration Assistant](../vm-management/vm-migration-assistant/vm-migration-assistant.md) to migrate
VMs to your VMO cluster, migration plans can enter an **Unknown** state if you have selected to migrate more VMs than
the **Max concurrent virtual machine migrations** setting allows.
VMs to your VMO cluster, migration plans can enter an **Unknown** state if more VMs are selected for migration than the
**Max concurrent virtual machine migrations** setting allows. This value determines the maximum number of VMs that can
be migrated simultaneously across all active migration plans.

To avoid this scenario, we recommend setting an appropriate value for **Max concurrent virtual machine migrations**
based on your workload and expected migration patterns. A higher value helps prevent migration plans from entering an
**Unknown** state due to excessive concurrency.

Use the following steps to adjust the value of **Max concurrent virtual machine migrations** and resolve the issue.
If migration plans do enter an **Unknown** state, use the following steps to resolve the issue.

### Debug Steps

Expand All @@ -34,10 +35,11 @@ Use the following steps to adjust the value of **Max concurrent virtual machine

4. Click the pencil icon next to the **Max concurrent virtual machine migrations** setting.

5. In the pop-up window, increase the value based on the maximum number of VMs you expect to migrate concurrently in a
single plan.
5. In the pop-up window, increase the value based on the maximum number of VMs you expect to migrate concurrently across
all active migration plans.

For example, if you expect to migrate a maximum of 25 VMs in a single plan, set this value to 25 or more.
For example, if you expect to migrate a maximum of 25 VMs across all active migration plans, set this value to 25 or
more.

6. Click **Save** after making the change.

Expand Down
Loading
Loading