Update cloud-init-troubleshooting.md #235
Conversation
Removed chroot from "Step3: Collect & review VM logs". Chroot isn't a requirement to access an oskdisk filesystem on a rescue VM. Using such could make troubleshooting more complicated if you intend on pulling off the logs in the advent of a support case requirement. Added simply mount to the section providing a link to the instruction for collecting and/or examining logs both LVM and Raw. Added cloud-init.log and cloud.init-output.log as these are part of the initial investigation. Added to "deeper dive" section serial logs as they are very important to look at for provisioning failures. Provided link how to access boot diagnostics (serial log) in the portal.
|
@mries : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 1cf7800:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/virtual-machines/linux/cloud-init-troubleshooting.md | Details |
articles/virtual-machines/linux/cloud-init-troubleshooting.md
- Line 91, Column 153: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 91, Column 309: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 112, Column 3: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 91, Column 153: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk' will be broken in isolated environments. Replace with a relative link. - Line 91, Column 309: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk' will be broken in isolated environments. Replace with a relative link. - Line 112, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Removed Localization from links (en-us)
|
Learn Build status updates of commit dff11da: 💡 Validation status: suggestions
articles/virtual-machines/linux/cloud-init-troubleshooting.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
let's wait on the review I am still have not making sure PG is good with the changes. |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
@mattmcinnes - Could you review this proposed update to your article and enter Thanks! |
github-actions
bot
removed
the
inactive
|
@mries -- review and accept these changes: |
|
Sorry for the delay. I will get a final review by PG this week. |
|
good to go according to PG. |
Co-authored-by: iamwilliew <[email protected]>
|
Learn Build status updates of commit c3f8307:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/virtual-machines/linux/cloud-init-troubleshooting.md | Details |
articles/virtual-machines/linux/cloud-init-troubleshooting.md
- Line 91, Column 153: [Warning: file-not-found - See documentation]
Invalid file link: 'troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux'. - Line 91, Column 275: [Warning: file-not-found - See documentation]
Invalid file link: 'troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux'. - Line 112, Column 3: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/virtual-machines/boot-diagnostics'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit f5935b8: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@mattmcinnes @cynthn - Can you review this proposed update to your article and enter |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
Removed chroot from "Step3: Collect & review VM logs". Chroot isn't a requirement to access an oskdisk filesystem on a rescue VM. Using such could make troubleshooting more complicated if you intend on pulling off the logs in the advent of a support case requirement.
Added simply mount to the section providing a link to the instruction for collecting and/or examining logs both LVM and Raw.
Added cloud-init.log and cloud.init-output.log as these are part of the initial investigation.
Added to "deeper dive" section serial logs as they are very important to look at for provisioning failures. Provided link how to access boot diagnostics (serial log) in the portal.