Skip to content

Conversation

@mries
Copy link
Contributor

@mries mries commented Dec 16, 2025

updated:
https://github.com/mries/azure-compute-docs/edit/main/articles/virtual-machines/linux/cloud-init-troubleshooting.md

in section:
https://github.com/mries/azure-compute-docs/edit/main/articles/virtual-machines/linux/cloud-init-troubleshooting.md#troubleshooting-failures-reported-by-cloud-init-and-logged-as-error

fixed MSP troubleshooting guide link (was 404)
added actual link to the cloud-init tracker reference in table.

added:
Some common issues can include:

  • The YAML is malformed
  • Scripts inside customData fail or hang
  • Override something cloud‑init relies on (for example, disk setup or networking)
  • The data contains unsupported characters or encoding problems

fixed broken markdown that creates a code block. spacing was incorrect.

updated:
https://github.com/mries/azure-compute-docs/edit/main/articles/virtual-machines/linux/cloud-init-troubleshooting.md

in section:
https://github.com/mries/azure-compute-docs/edit/main/articles/virtual-machines/linux/cloud-init-troubleshooting.md#troubleshooting-failures-reported-by-cloud-init-and-logged-as-error

fixed MSP troubleshooting guide link (was 404)
added actual link to the cloud-init tracker reference in table.

added:
Some common issues can include:
- [The YAML is malformed](https://cloudinit.readthedocs.io/en/latest/howto/debug_user_data.html)
- Scripts inside customData fail or hang
- Override something cloud‑init relies on (for example, disk setup or networking)
- The data contains unsupported characters or encoding problems

fixed broken markdown that creates a code block.  spacing was incorrect.
Revise cloud-init troubleshooting documentation
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 7233c3f:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/virtual-machines/linux/cloud-init-troubleshooting.md ⚠️Warning Details

articles/virtual-machines/linux/cloud-init-troubleshooting.md

  • Line 49, Column 166: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 50, Column 159: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 49, Column 166: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide' will be broken in isolated environments. Replace with a relative link.
  • Line 50, Column 159: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide' 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.

fixed localization problems in links
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit ebcbece:

💡 Validation status: suggestions

File Status Preview URL Details
articles/virtual-machines/linux/cloud-init-troubleshooting.md 💡Suggestion Details

articles/virtual-machines/linux/cloud-init-troubleshooting.md

  • Line 49, Column 166: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide' will be broken in isolated environments. Replace with a relative link.
  • Line 50, Column 159: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide' 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.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 1ce8850:

💡 Validation status: suggestions

File Status Preview URL Details
articles/virtual-machines/linux/cloud-init-troubleshooting.md 💡Suggestion Details

articles/virtual-machines/linux/cloud-init-troubleshooting.md

  • Line 49, Column 166: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide/' will be broken in isolated environments. Replace with a relative link.
  • Line 50, Column 159: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide/' 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.

@v-dirichards
Copy link
Contributor

v-dirichards commented Dec 16, 2025

@mries -- It looks like you have access to the private repo, and if so - you should use that for content updates. I'll leave this open in case @mattmcinnes wants to review it, but in the future you should submit changes to the private repo: azure-compute-docs-pr.


@mattmcinnes

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 C+L Pull Request Review Team label label Dec 16, 2025
@prmerger-automator
Copy link
Contributor

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

@mries
Copy link
Contributor Author

mries commented Dec 16, 2025

@mries -- It looks like you have access to the private repo, and if so - you should use that for content updates. I'll leave this open in case @mattmcinnes wants to review it, but in the future you should submit changes to the private repo: azure-compute-docs-pr.

@mattmcinnes

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-t

@mries mries closed this Dec 16, 2025
@mries
Copy link
Contributor Author

mries commented Dec 16, 2025

@mries -- It looks like you have access to the private repo, and if so - you should use that for content updates. I'll leave this open in case @mattmcinnes wants to review it, but in the future you should submit changes to the private repo: azure-compute-docs-pr.
@mattmcinnes
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-t

@mries mries reopened this Dec 16, 2025
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 1ce8850:

💡 Validation status: suggestions

File Status Preview URL Details
articles/virtual-machines/linux/cloud-init-troubleshooting.md 💡Suggestion Details

articles/virtual-machines/linux/cloud-init-troubleshooting.md

  • Line 49, Column 166: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide/' will be broken in isolated environments. Replace with a relative link.
  • Line 50, Column 159: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/virtual-machines/metadata-security-protocol/troubleshoot-guide/' 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.

@mries
Copy link
Contributor Author

mries commented Dec 16, 2025

@v-dirichards , yeah not sure what happened. I thought I performed the PR that way. I will review my steps. by the way I deleted some text from the end of the line: "#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-t". I was going to reply directly to your comment however the I seemed to delete some of the end.

@v-dirichards
Copy link
Contributor

@mries If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.

After you move the commits or make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.

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