-
Notifications
You must be signed in to change notification settings - Fork 418
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
base: main
Are you sure you want to change the base?
Conversation
Known issue documented internally and must be published here for customers: https://internal.evergreen.microsoft.com/en-us/topic/8ac50cf1-8e25-005b-9a01-4b0a8a791ab7
@SharmaKartikay : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 30c5d0f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this 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 | |||
|
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. | ||
|
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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.
[like] Kartikay Sharma reacted to your message:
________________________________
From: Alpa Kohli ***@***.***>
Sent: Friday, May 30, 2025 5:35:33 PM
To: MicrosoftDocs/azure-stack-docs ***@***.***>
Cc: Kartikay Sharma ***@***.***>; Mention ***@***.***>
Subject: Re: [MicrosoftDocs/azure-stack-docs] Update troubleshoot-arc-enabled-vms.md (PR #3618)
@alkohli commented on this pull request.
Thank you for your contribution @SharmaKartikay<https://github.com/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.
________________________________
In azure-local/manage/troubleshoot-arc-enabled-vms.md<#3618 (comment)>:
@@ -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
+
Change the title to: Live migrations on Azure Local 2311.2 and later could fail without error
________________________________
In azure-local/manage/troubleshoot-arc-enabled-vms.md<#3618 (comment)>:
@@ -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.
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.
________________________________
In azure-local/manage/troubleshoot-arc-enabled-vms.md<#3618 (comment)>:
@@ -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.
+
+**Issue:** Live migration attempts may fail silently — no error messages are logged.
+
Add: Cause:
________________________________
In azure-local/manage/troubleshoot-arc-enabled-vms.md<#3618 (comment)>:
@@ -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.
+
+**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.
Change: This problem is caused by a known issue in Azure Local, version 2311.2 or later. This problem manifests under specific system configurations.
________________________________
In azure-local/manage/troubleshoot-arc-enabled-vms.md<#3618 (comment)>:
@@ -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.
+
+**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.
+
+**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.
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.
—
Reply to this email directly, view it on GitHub<#3618 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKXDMT3YSY5GWF7WMMQT2ED3BCJGLAVCNFSM6AAAAAB3Y3SGASVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDQOBRHEYDIMBRGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@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 #label:"aq-pr-triaged" |
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