Skip to content

Update repair-linux-vm-using-azure-virtual-machine-repair-commands.md #1865

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

Merged
merged 6 commits into from
Apr 29, 2025

Conversation

saloni-mehta52
Copy link
Contributor

The scripts cannot run with only VM Contributor role access as it requires read, write, delete operations at resource group level.

Pull request guidance

Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.

We also need your help in order to process your request as soon as possible:

  • We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

  • After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

The scripts cannot run with only VM Contributor role access as it requires read, write, delete operations at resource group level.
Copy link

@saloni-mehta52 : 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 c20b0fd:

✅ Validation status: passed

File Status Preview URL Details
support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

Learn Build status updates of commit 8b457bc:

✅ Validation status: passed

File Status Preview URL Details
support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

Learn Build status updates of commit 89dfa81:

✅ Validation status: passed

File Status Preview URL Details
support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

Learn Build status updates of commit 200c02d:

✅ Validation status: passed

File Status Preview URL Details
support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

Learn Build status updates of commit e07bc9a:

⚠️ Validation status: warnings

File Status Preview URL Details
support/azure/virtual-machines/linux/troubleshoot-pacemaker-services-suse.md ⚠️Warning Details
support/azure/virtual-machines/linux/troubleshoot-rhel-pacemaker-cluster-services-resources-startup-issues.md ⚠️Warning Details
support/sql/releases/sqlserver-2016/rtm-cumulativeupdate5.md ⚠️Warning Details
support/sql/releases/sqlserver-2016/servicepack1-cumulativeupdate2.md ⚠️Warning Details
support/windows-server/networking/dns-zone-transfer-fails-only-servers-listed-name-servers.md ⚠️Warning Details
support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md ✅Succeeded

support/azure/virtual-machines/linux/troubleshoot-pacemaker-services-suse.md

  • Line 308, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'master/slave' is sensitive and should not be used in content or code. Usage: ' Master/Slave Set: msl_SAPHana [rsc_SAPHana]'

support/azure/virtual-machines/linux/troubleshoot-rhel-pacemaker-cluster-services-resources-startup-issues.md

  • Line 273, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'slave' is sensitive and should not be used in content or code. Usage: ' + hana_XXX_roles : 2:P:master1:master:worker:slave'
  • Line 278, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'slave' is sensitive and should not be used in content or code. Usage: ' + hana_XXX_roles : 2:S:master1:master:worker:slave'
  • Line 297, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'master/slave' is sensitive and should not be used in content or code. Usage: ' Master/Slave Set: msl_SAPHana [rsc_SAPHana]'
  • Line 299, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'slave' is sensitive and should not be used in content or code. Usage: ' Slave: [ node-0 ]'

support/sql/releases/sqlserver-2016/rtm-cumulativeupdate5.md

  • Line 72, Column 1: [Warning: sensitive-language-ma - See documentation] Term 'master server' is sensitive and should not be used in content or code. Usage: '8](#9503258) </a> | [FIX: The sp_msx_enlist stored procedure fails to enlist a target server into a master server in SQL Server 2014 or 2016 if the server name is too long (KB4010344)](https://support.microsoft.co'

support/sql/releases/sqlserver-2016/servicepack1-cumulativeupdate2.md

  • Line 63, Column 1: [Warning: sensitive-language-ma - See documentation] Term 'master server' is sensitive and should not be used in content or code. Usage: '59](#9503259)</a> | [FIX: The sp_msx_enlist stored procedure fails to enlist a target server into a master server in SQL Server 2014 or 2016 if the server name is too long (KB4010344)](https://support.microsoft.co'

support/windows-server/networking/dns-zone-transfer-fails-only-servers-listed-name-servers.md

  • Line 20, Column 1: [Warning: sensitive-language-ma - See documentation] Term 'master server' is sensitive and should not be used in content or code. Usage: ' server encountered a problem while attempting to load the zone. The transfer of zone data from the master server failed. '

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:

@genlin genlin merged commit ae1273e into MicrosoftDocs:main Apr 29, 2025
1 of 2 checks passed
Copy link
Contributor

Learn Build status updates of commit 04aabac:

⚠️ Validation status: warnings

File Status Preview URL Details
support/azure/virtual-machines/linux/troubleshoot-pacemaker-services-suse.md ⚠️Warning Details
support/azure/virtual-machines/linux/troubleshoot-rhel-pacemaker-cluster-services-resources-startup-issues.md ⚠️Warning Details
support/sql/releases/sqlserver-2016/rtm-cumulativeupdate5.md ⚠️Warning Details
support/sql/releases/sqlserver-2016/servicepack1-cumulativeupdate2.md ⚠️Warning Details
support/windows-server/networking/dns-zone-transfer-fails-only-servers-listed-name-servers.md ⚠️Warning Details
support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md ✅Succeeded

support/azure/virtual-machines/linux/troubleshoot-pacemaker-services-suse.md

  • Line 308, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'master/slave' is sensitive and should not be used in content or code. Usage: ' Master/Slave Set: msl_SAPHana [rsc_SAPHana]'

support/azure/virtual-machines/linux/troubleshoot-rhel-pacemaker-cluster-services-resources-startup-issues.md

  • Line 273, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'slave' is sensitive and should not be used in content or code. Usage: ' + hana_XXX_roles : 2:P:master1:master:worker:slave'
  • Line 278, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'slave' is sensitive and should not be used in content or code. Usage: ' + hana_XXX_roles : 2:S:master1:master:worker:slave'
  • Line 297, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'master/slave' is sensitive and should not be used in content or code. Usage: ' Master/Slave Set: msl_SAPHana [rsc_SAPHana]'
  • Line 299, Column 1: [Warning: sensitive-language-sl - See documentation] Term 'slave' is sensitive and should not be used in content or code. Usage: ' Slave: [ node-0 ]'

support/sql/releases/sqlserver-2016/rtm-cumulativeupdate5.md

  • Line 72, Column 1: [Warning: sensitive-language-ma - See documentation] Term 'master server' is sensitive and should not be used in content or code. Usage: '8](#9503258) </a> | [FIX: The sp_msx_enlist stored procedure fails to enlist a target server into a master server in SQL Server 2014 or 2016 if the server name is too long (KB4010344)](https://support.microsoft.co'

support/sql/releases/sqlserver-2016/servicepack1-cumulativeupdate2.md

  • Line 63, Column 1: [Warning: sensitive-language-ma - See documentation] Term 'master server' is sensitive and should not be used in content or code. Usage: '59](#9503259)</a> | [FIX: The sp_msx_enlist stored procedure fails to enlist a target server into a master server in SQL Server 2014 or 2016 if the server name is too long (KB4010344)](https://support.microsoft.co'

support/windows-server/networking/dns-zone-transfer-fails-only-servers-listed-name-servers.md

  • Line 20, Column 1: [Warning: sensitive-language-ma - See documentation] Term 'master server' is sensitive and should not be used in content or code. Usage: ' server encountered a problem while attempting to load the zone. The transfer of zone data from the master server failed. '

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:

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.

2 participants