An unexpected error occured while processing the network profile of the VM. Please retry later.

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name az vm create

Errors:

Deployment failed. Correlation ID: 2ff74f6d-9636-434e-a772-ea3bd265ba7d. {
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "NetworkingInternalOperationError",
        "message": "An unexpected error occured while processing the network profile of the VM. Please retry later."
      }
    ]
  }
}

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here…
az vm create --subscription {} --location {} --resource-group {} --name {} --image {} --size {} --generate-ssh-keys --output {}

Expected Behavior

Environment Summary

Linux-5.0.0-1032-azure-x86_64-with-Ubuntu-18.04-bionic
Python 3.6.9

azure-cli 2.2.0

Additional Context

I get this error quite often. I think I have this error only when I try to make a VM on eastus2.

Issue Analytics

State:
Created 3 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

JoeSainsburyscommented, Apr 30, 2020

I chased this up with MS and they seem to have found the issue and are in the process of fixing it

Hi Joe,

I hope this e-mail finds you well

Thank you for your quick response and I am glad that the issue is fixed . The Microsoft Azure Platform team has investigated the issue which affected the Virtual Machine management operations like start/deallocate/delete. Our investigation determined that the VIPs allocated to these deployments were not released by backend networking component on time due to a bug in the code which handles the release requests.   We have identified a fix for this issue which will roll out to production over the next 2 weeks following safe deployment process.  Until fully deployed, we are running multiple daily scans to identify impacted resources and mitigate them proactively.  We apologize for any inconvenience that may have been caused by this behavior Please let me know if you have other questions to continue troubleshooting or mark this case as resolved .

0reactions

bart986commented, Jul 29, 2020

Hello, Allow me to share similar issue with our VMSS. It is pretty stable and each day it is being started and stopped by runbooks that twe hold in automation account. Until today: without particular reason vmss didn’t start instance today, when I checked erorrs in jobs I found: looks like internal microsoft error, vmss is completly frozen, restarting, stopping, starting each instance takes around 55minutes and fails each time, same when I try to restart vmss service. It is huge P0 situation because this vmss corsponds to aks for our dev environment, would be great it any Azure tech specialist could have a look on that