TK82665AKSRVWTSGCNIDWTIOUTVMEXERR #1678
Conversation
Reviewing the article in detail to identify if any changes are needed. Tasks by Rekha Nain (v-rekhanain).
|
@azmmft : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 0decf98: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
| @@ -10,7 +10,7 @@ ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool | |||
| --- | |||
| # Troubleshoot the CniDownloadTimeoutVMExtensionError error code (41) | |||
|
|
|||
| This article discusses how to identify and resolve the `CniDownloadTimeoutVMExtensionError` error (also known as error code `ERR_CNI_DOWNLOAD_TIMEOUT`, error number 41) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster. | |||
| This article discusses how to identify and resolve the `CniDownloadTimeoutVMExtensionError` error (also known as error code `ERR_CNI_DOWNLOAD_TIMEOUT`, error number `41` when uses linux distros or error number `35` to the windows nodes) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster. | |||
There was a problem hiding this comment.
should we change to:
This article discusses how to identify and resolve the CniDownloadTimeoutVMExtensionError error (also known as error code ERR_CNI_DOWNLOAD_TIMEOUT, error number 41 when uses linux distros) or error (also known as error code WINDOWS_CSE_ERROR_DOWNLOAD_CNI_PACKAGE , error number 35 to the windows nodes) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
$global:WINDOWS_CSE_ERROR_DOWNLOAD_CNI_PACKAGE=35 https://github.com/Azure/AgentBaker/blob/2a43850ca0495eadf9050e54d3292d3eeaf66049/parts/windows/windowscsehelper.ps1#L41
There was a problem hiding this comment.
@genlin what do you think
Reviewing the article in detail to identify if any changes are needed. Tasks by Rekha Nain (v-rekhanain).
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.