Skip to content

Update troubleshoot-arc-enabled-vms.md #3618

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SharmaKartikay
Copy link
Contributor

Known issue documented internally and must be published here for customers. Refer: https://internal.evergreen.microsoft.com/en-us/topic/8ac50cf1-8e25-005b-9a01-4b0a8a791ab7

Copy link
Contributor

@SharmaKartikay : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 30c5d0f:

✅ Validation status: passed

File Status Preview URL Details
azure-local/manage/troubleshoot-arc-enabled-vms.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@alkohli

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged Tracking label for the PR review team label Apr 24, 2025
Copy link
Contributor

@alkohli alkohli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution @SharmaKartikay. There are few changes that will need to be made. We will be making these changes in another PR and will merge it after we have the PM approval.

@@ -128,6 +128,35 @@ If your environment fails to recognize Azure CLI after installing it, run the fo
}
```

## Live Migrations on Azure Local 23H2 May Fail Without Error

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change the title to: Live migrations on Azure Local 2311.2 and later could fail without error

@@ -128,6 +128,35 @@ If your environment fails to recognize Azure CLI after installing it, run the fo
}
```

## Live Migrations on Azure Local 23H2 May Fail Without Error

After upgrading from Azure Local 22H2 to 23H2, or on a clean install of 23H2, you may encounter issues where VMs fail to live migrate in an Azure Local Cluster.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change to: After you upgrade to Azure Local 2311.2 or on a new deployment of 2311.2 or later, you could see issues where the Azure Local VMs fail to live migrate in an Azure Local instance.

After upgrading from Azure Local 22H2 to 23H2, or on a clean install of 23H2, you may encounter issues where VMs fail to live migrate in an Azure Local Cluster.

**Issue:** Live migration attempts may fail silently — no error messages are logged.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add: Cause:


**Issue:** Live migration attempts may fail silently — no error messages are logged.

This problem is caused by a known issue in Azure Local 23H2 that manifests under specific system configurations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change: This problem is caused by a known issue in Azure Local, version 2311.2 or later. This problem manifests under specific system configurations.


**Resolution:**

Run the following PowerShell script locally on one of the cluster nodes. This script will apply a registry fix on all nodes. After running it, reboot each node one at a time for the change to take effect.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change: Run the following PowerShell script locally on one of the Azure Local machines. This script applies a registry fix on all the machines of your Azure Local instance.

After you have run the script, reboot each machine one at a time for the change to take effect.

@SharmaKartikay
Copy link
Contributor Author

SharmaKartikay commented Jun 2, 2025 via email

@v-dirichards
Copy link
Contributor

@SharmaKartikay - Can you respond to the requested changes or let us know if you would like us to commit them?

@alkohli - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants