How do I prevent: VMExtensionProvisioningTimeout

Open
#172 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, linux, shell

Research direction

Start with the deployment error and the linked VM extension troubleshooting guidance at https://aka.ms/VMExtensionCSELinuxTroubleshoot. Determine whether periodic Azure provisioning updates or a reboot can extend this extension's timeout, and document the supported behavior or required change for scripts running longer than 90 minutes.

Written by the indexing model from the issue text.

Description

My extension script for linux is working just fine, its just that it takes more than 90 minutes to complete or maybe its because at the end of the script there is a reboot command to reboot the server.

Is there a way this script can do periodic curl POST to some api in azure provisioning to let it know its install is progressing well so that azure does not report this error? The install works great, its just that azure is reporting this error.

I get the following deployment error

{
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The resource operation completed with terminal provisioning state 'Failed'.",
        "details": [
            {
                "code": "VMExtensionProvisioningTimeout",
                "message": "Provisioning of VM extension InstallLinuxSrvTierAddons.sh has timed out. Extension provisioning has taken too long to complete. The extension last reported \"Plugin enabled\".\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot"
            }
        ]
    }
}
Dominant language
Go
Stars
113
Forks
46
Avg merge
4d 15h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/custom-script-extension-linux

All issues in Azure/custom-script-extension-linux

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.