Update vm-extension-provisioning-errors.md #1787
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When troubleshooting a case, I got into scenario where cx encountered OSProvisioningTimedOut for VMSS SCALE-in and cx referred our MS public doc to exactly check what would be timeout period and cx could not find any MS Public doc mentioning it and cx is very upset that our doc is not properly updated as this is very common error scenario . So updated the public doc with below info with 2 scenarios of timeout periods as well which would be helpful for any cx's checking the same. In some circumstances Instance VM scalein for VMSS, virtual machine deployment will fail with the message "OSProvisioningTimedOut". Most of the time, the virtual machine should be started and the operating system running. The Guest Agent should often report status as well.This error appears usually when the Provisioning Agent or the Guest Agent can't send status back to CRP but the virtual machine has been created and the operating system started. The timeout set for CRP to wait for the VM Guest OS to send a healthy signal is 40 minutes, if the VM Deployed includes Extensions the timeout is extended to wait for 90 minutes. This time might change at any time.
|
@Padmini2303 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 1e2823e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When troubleshooting a case, I got into scenario where cx encountered OSProvisioningTimedOut for VMSS SCALE-in and cx referred our MS public doc to exactly check what would be timeout period and cx could not find any MS Public doc mentioning it and cx is very upset that our doc is not properly updated as this is very common error scenario .
So updated the public doc with below info with 2 scenarios of timeout periods as well which would be helpful for any cx's checking the same.
In some circumstances Instance VM scalein for VMSS, virtual machine deployment will fail with the message "OSProvisioningTimedOut". Most of the time, the virtual machine should be started and the operating system running. The Guest Agent should often report status as well.This error appears usually when the Provisioning Agent or the Guest Agent can't send status back to CRP but the virtual machine has been created and the operating system started. The timeout set for CRP to wait for the VM Guest OS to send a healthy signal is 40 minutes, if the VM Deployed includes Extensions the timeout is extended to wait for 90 minutes. This time might change at any time.
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.