none
azure ARM vm start results in Unknown network allocation error RRS feed

  • Question

  • I'm seeing that my VMs are not starting anymore. I had shut them down on Friday and on Monday when I try to start them, they go back to Failed Provisioning State....very weird...

    I don't see any other error messages in Event Log. By running with -vv, I see it returns :

    "code": "NetworkingInternalOperationError",\015\n    "message": "Unknown network allocation error.

    I think this is a bug in Azure and we shouldn't need to recover the VMs. This is basic operation.

    SJCMAC9X2DG3QJ:azure samisra$ azure vm start -g SM-SFHACK -n myFW

    info:    Executing command vm start

    + Looking up the VM "myFW"                                                     

    + Starting the virtual machine "myFW"                                          

    info:    vm start command OK

    SJCMAC9X2DG3QJ:azure samisra$ azure vm list 

    info:    Executing command vm list

    + Getting virtual machines                                                     

    data:    Name         ProvisioningState  PowerState      Location  Size       

    data:    -----------  -----------------  --------------  --------  -----------

    data:    myFW         Failed                             westus    Standard_A4

    data:    myUbuntuSM0  Succeeded          VM deallocated  westus    Standard_A3

    data:    myUbuntuSM1  Succeeded          VM deallocated  westus    Standard_A3

    info:    vm list command OK

    SJCMAC9X2DG3QJ:azure samisra$ azure vm start -g SM-SFHACK -n myFW -vv

    info:    Executing command vm start

    verbose: Looking up the VM "myFW"

    silly:   requestOptions

    silly:   {

    silly:       rawResponse: false,

    silly:       queryString: {},

    silly:       method: 'GET',

    silly:       headers: { Content-Type: 'application/json' },

    silly:       url: 'https://management.azure.com/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/resourceGroups/SM-SFHACK/providers/Microsoft.Compute/virtualMachines/myFW?api-version=2015-06-15'

    silly:   }

    silly:   returnObject

    silly:   {

    silly:       statusCode: 200,

    silly:       header: {

    silly:           cache-control: 'no-cache',

    silly:           pragma: 'no-cache',

    silly:           content-length: '1791',

    silly:           content-type: 'application/json; charset=utf-8',

    silly:           expires: '-1',

    silly:           strict-transport-security: 'max-age=31536000; includeSubDomains',

    silly:           x-ms-served-by: 'e3cb9db0-bac5-4364-b92c-b5196ffd5a7c_130925340114062436',

    silly:           x-ms-request-id: '6181a588-238f-4123-8170-df9ce294adde',

    silly:           server: 'Microsoft-HTTPAPI/2.0, Microsoft-HTTPAPI/2.0',

    silly:           x-ms-ratelimit-remaining-subscription-reads: '14949',

    silly:           x-ms-correlation-request-id: '97b52b0f-8acb-4fbd-b384-78122e09359d',

    silly:           x-ms-routing-request-id: 'NORTHCENTRALUS:20151214T180000Z:97b52b0f-8acb-4fbd-b384-78122e09359d',

    silly:           date: 'Mon, 14 Dec 2015 18:00:00 GMT',

    silly:           connection: 'close'

    silly:       },

    silly:       body: '{\015\n  "properties": {\015\n    "vmId": "ba1037bb-fab7-415b-8e6c-fe58f7b30dac",\015\n    "hardwareProfile": {\015\n      "vmSize": "Standard_A4"\015\n    },\015\n    "storageProfile": {\015\n      "osDisk": {\015\n        "osType": "Linux",\015\n        "name": "myFW-osDisk",\015\n        "createOption": "FromImage",\015\n        "image": {\015\n          "uri": "http://smstorage1215.blob.core.windows.net/images/sm-pavm1-blob1.vhd"\015\n        },\015\n        "vhd": {\015\n          "uri": "http://smstorage1215.blob.core.windows.net/vhds/myFWosDisk.vhd"\015\n        },\015\n        "caching": "ReadWrite"\015\n      },\015\n      "dataDisks": []\015\n    },\015\n    "osProfile": {\015\n      "computerName": "myFW",\015\n      "adminUsername": "samisra",\015\n      "linuxConfiguration": {\015\n        "disablePasswordAuthentication": false\015\n      },\015\n      "secrets": []\015\n    },\015\n    "networkProfile": {"networkInterfaces":[{"id":"/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/resourceGroups/SM-SFHACK/providers/Microsoft.Network/networkInterfaces/FWeth0","properties":{"primary":true}},{"id":"/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/resourceGroups/SM-SFHACK/providers/Microsoft.Network/networkInterfaces/FWeth1","properties":{"primary":false}},{"id":"/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/resourceGroups/SM-SFHACK/providers/Microsoft.Network/networkInterfaces/FWeth2","properties":{"primary":false}},{"id":"/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/resourceGroups/SM-SFHACK/providers/Microsoft.Network/networkInterfaces/FWeth3","properties":{"primary":false}}]},\015\n    "provisioningState": "Failed"\015\n  },\015\n  "id": "/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/resourceGroups/SM-SFHACK/providers/Microsoft.Compute/virtualMachines/myFW",\015\n  "name": "myFW",\015\n  "type": "Microsoft.Compute/virtualMachines",\015\n  "location": "westus"\015\n}'

    silly:   }

    verbose: Starting the virtual machine "myFW"

    silly:   requestOptions

    silly:   {

    silly:       rawResponse: false,

    silly:       queryString: {},

    silly:       method: 'POST',

    silly:       headers: {},

    silly:       url: 'https://management.azure.com/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/resourceGroups/SM-SFHACK/providers/Microsoft.Compute/virtualMachines/myFW/start?api-version=2015-06-15'

    silly:   }

    silly:   returnObject

    silly:   {

    silly:       statusCode: 202,

    silly:       header: {

    silly:           cache-control: 'no-cache',

    silly:           pragma: 'no-cache',

    silly:           content-length: '0',

    silly:           expires: '-1',

    silly:           location: 'https://management.azure.com/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/providers/Microsoft.Compute/locations/westus/operations/e52defb3-ec9e-405d-910d-f03696aec52f?monitor=true&api-version=2015-06-15',

    silly:           azure-asyncoperation: 'https://management.azure.com/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/providers/Microsoft.Compute/locations/westus/operations/e52defb3-ec9e-405d-910d-f03696aec52f?api-version=2015-06-15',

    silly:           strict-transport-security: 'max-age=31536000; includeSubDomains',

    silly:           x-ms-served-by: 'e3cb9db0-bac5-4364-b92c-b5196ffd5a7c_130925340114062436',

    silly:           x-ms-request-id: 'e52defb3-ec9e-405d-910d-f03696aec52f',

    silly:           server: 'Microsoft-HTTPAPI/2.0, Microsoft-HTTPAPI/2.0',

    silly:           x-ms-ratelimit-remaining-subscription-writes: '1199',

    silly:           x-ms-correlation-request-id: '05b5f3aa-4df9-4bc2-854f-a43a386a8cbb',

    silly:           x-ms-routing-request-id: 'NORTHCENTRALUS:20151214T180001Z:05b5f3aa-4df9-4bc2-854f-a43a386a8cbb',

    silly:           date: 'Mon, 14 Dec 2015 18:00:01 GMT',

    silly:           connection: 'close'

    silly:       },

    silly:       body: ''

    silly:   }

    silly:   requestOptions

    silly:   {

    silly:       rawResponse: false,

    silly:       queryString: {},

    silly:       method: 'GET',

    silly:       headers: {},

    silly:       url: 'https://management.azure.com/subscriptions/93f083c5-7cd6-4fe2-b746-ab91a3e5d6e3/providers/Microsoft.Compute/locations/westus/operations/e52defb3-ec9e-405d-910d-f03696aec52f?api-version=2015-06-15'

    silly:   }

    silly:   returnObject

    silly:   {

    silly:       statusCode: 200,

    silly:       header: {

    silly:           cache-control: 'no-cache',

    silly:           pragma: 'no-cache',

    silly:           content-length: '309',

    silly:           content-type: 'application/json; charset=utf-8',

    silly:           expires: '-1',

    silly:           retry-after: '480',

    silly:           strict-transport-security: 'max-age=31536000; includeSubDomains',

    silly:           x-ms-served-by: 'e3cb9db0-bac5-4364-b92c-b5196ffd5a7c_130925340114062436',

    silly:           x-ms-request-id: '3a18d23c-d419-41f2-8bfe-4715bfbaf727',

    silly:           server: 'Microsoft-HTTPAPI/2.0, Microsoft-HTTPAPI/2.0',

    silly:           x-ms-ratelimit-remaining-subscription-reads: '14996',

    silly:           x-ms-correlation-request-id: 'e8a165ba-7d5f-4882-9de5-57abce216554',

    silly:           x-ms-routing-request-id: 'NORTHCENTRALUS:20151214T180032Z:e8a165ba-7d5f-4882-9de5-57abce216554',

    silly:           date: 'Mon, 14 Dec 2015 18:00:31 GMT',

    silly:           connection: 'close'

    silly:       },

    silly:       body: '{\015\n  "operationId": "e52defb3-ec9e-405d-910d-f03696aec52f",\015\n  "status": "Failed",\015\n  "startTime": "2015-12-14T18:00:00.1440697+00:00",\015\n  "endTime": "2015-12-14T18:00:01.9090386+00:00",\015\n  "error": {\015\n    "code": "NetworkingInternalOperationError",\015\n    "message": "Unknown network allocation error."\015\n  }\015\n}'

    silly:   }

    info:    vm start command OK

    SJCMAC9X2DG3QJ:azure samisra$ 

    Monday, December 14, 2015 6:08 PM

All replies

  • Hello Saurabh Mishra,

    1. Which regions do you have these Virtual Machines deployed in?
    2. What type of account do you have for your subscription?

    I suggest that you manually try from the Azure portal to see if you are able to start the Virtual Machines.

    Thanks,
    Syed Irfan Hussain

    Tuesday, December 15, 2015 2:16 PM
    Moderator
  • location is westus. It's already there in the output. I've already tried portal and only then I went to Azure CLI.  So isn't CLI, Powershell and portal should behave the same way? or Each tools in Azure is suppose to do things differently?

    Tuesday, December 15, 2015 5:21 PM
  • Hello Saurabh Mishra,

    There is no difference in terms of how the portal would behave from CLIs. Just wanted to be sure that the issue is not on the client end. We will need to check the status of the node. Please let me know if you have a Technical Support plan.

    If you have a Technical Support plan, I request you to create a Support ticket following the link below:
    https://azure.microsoft.com/en-in/support/options/

    If you don't have a support plan, you can run the Software diagnostic package to recover your Virtual Machine. The Troubleshooter will attempt to recover VMs by attaching their OS disks as a data disk to a new Recovery VM.

    You to download the diagnostic package by following the instructions given in the link below:

    http://social.technet.microsoft.com/wiki/contents/articles/26465.azure-iaas-windows-diagnostic-package.aspx

    a. Once you have the packaged downloaded, you will need to authenticate your subscription using the credentials
    b. Select the storage account and select the effected virtual machine, please note that you will be able to access multiple virtual machines simultaneously.


    You will be prompted to enter a username and password for use with creating the recovery VM.


    Thanks,
    Syed Irfan Hussain

    Wednesday, December 16, 2015 10:32 AM
    Moderator