Skip to content

KI for 2506 #3745

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

Closed
wants to merge 2 commits into from
Closed

KI for 2506 #3745

wants to merge 2 commits into from

Conversation

ManikaDhiman
Copy link
Contributor

No description provided.

Copy link
Contributor

@ManikaDhiman : 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 d0b5409:

✅ Validation status: passed

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

For more details, please refer to the build report.

Copy link
Contributor

Learn Build status updates of commit d628e90:

✅ Validation status: passed

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

For more details, please refer to the build report.

@@ -187,6 +186,65 @@ To resolve this issue, follow these steps:

1. Restart the VM. After the restart, the warning message should no longer appear.

## VMs and VHDs deployed without a specified storage path landing only on the first storage path in the cluster

**Error:**

Choose a reason for hiding this comment

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

image

Choose a reason for hiding this comment

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

^ from offline discussion with Alpa. Change REDACTED to Azure resource name and add the blurb after to describe the error more, as the error message provided can be covered for other scenarios as well.

@ttorble
Copy link
Contributor

ttorble commented Jul 21, 2025

@ManikaDhiman did you intend to open this PR in the private repo? It looks like you have access to the private repo, and if so, you should use that for content updates. I'll close this PR. Thanks.

@ttorble ttorble closed this Jul 21, 2025
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.

4 participants