locked
Azure Stack - "code": "ResourceDeploymentFailure" "message": "The resource operation completed with terminal provisioning state 'Failed'." RRS feed

  • Question

  • Hi

    Using Azure Cli we are currently encountering the following issue with AzureStack. We are running the following commands:

    az cloud register -n AzureStack (relevant parameters)
    az cloud set -n AzureStack
    az cloud update --profile 2017-03-09-profile
    az login -u username -p password
    az group create --name pkb05333d87-cassandra_stress0 --location location01
    az group show --name pkb05333d87-cassandra_stress0
    az vm availability-set create --resource-group pkb05333d87-cassandra_stress0 --name pkb05333d87-cassandra_stress0 --location location01
    az vm availability-set show --output json --resource-group pkb05333d87-cassandra_stress0 --name pkb05333d87-cassandra_stress0
    az storage account create --kind Storage --sku Standard_LRS --name pkb05333d87storage0 --resource-group pkb05333d87-cassandra_stress0 --location location01
    az storage account show --output json --name pkb05333d87storage0 --resource-group pkb05333d87-cassandra_stress0
    az storage account show-connection-string --output json --name pkb05333d87storage0 --resource-group pkb05333d87-cassandra_stress0
    az storage account keys list --output json --account-name pkb05333d87storage0 --resource-group pkb05333d87-cassandra_stress0
    az network vnet create --location location01 --address-prefixes 10.0.0.0/16 --name pkb05333d87-cassandra_stress0-location01-vnet --resource-group pkb05333d87-cassandra_stress0
    az network vnet show --output json --name pkb05333d87-cassandra_stress0-location01-vnet --resource-group pkb05333d87-cassandra_stress0
    az network vnet subnet create --vnet-name pkb05333d87-cassandra_stress0-location01-vnet --address-prefix 10.0.0.0/16 --name pkb05333d87-cassandra_stress0-location01-vnet-subnet --resource-group pkb05333d87-cassandra_stress0
    az network vnet subnet show --vnet-name pkb05333d87-cassandra_stress0-location01-vnet --output json --name pkb05333d87-cassandra_stress0-location01-vnet-subnet --resource-group pkb05333d87-cassandra_stress0
    az network nsg create --location location01 --name pkb05333d87-cassandra_stress0-location01-vnet-subnet-nsg --resource-group pkb05333d87-cassandra_stress0
    az network nsg show --output json --name pkb05333d87-cassandra_stress0-location01-vnet-subnet-nsg --resource-group pkb05333d87-cassandra_stress0
    az network vnet subnet update --name pkb05333d87-cassandra_stress0-location01-vnet-subnet --network-security-group pkb05333d87-cassandra_stress0-location01-vnet-subnet-nsg --resource-group pkb05333d87-cassandra_stress0 --vnet-name pkb05333d87-cassandra_stress0-location01-vnet
    az network public-ip create --location location01 --name pkb-05333d87-3-public-ip --resource-group pkb05333d87-cassandra_stress0
    az network public-ip create --location location01 --name pkb-05333d87-1-public-ip --resource-group pkb05333d87-cassandra_stress0
    az network public-ip show --output json --name pkb-05333d87-3-public-ip --resource-group pkb05333d87-cassandra_stress0
    az network public-ip show --output json --name pkb-05333d87-1-public-ip --resource-group pkb05333d87-cassandra_stress0
    az network nic create --location location01 --vnet-name pkb05333d87-cassandra_stress0-location01-vnet --subnet pkb05333d87-cassandra_stress0-location01-vnet-subnet --public-ip-address pkb-05333d87-3-public-ip --name pkb-05333d87-3-nic --resource-group pkb05333d87-cassandra_stress0
    az network nic create --location location01 --vnet-name pkb05333d87-cassandra_stress0-location01-vnet --subnet pkb05333d87-cassandra_stress0-location01-vnet-subnet --public-ip-address pkb-05333d87-1-public-ip --name pkb-05333d87-1-nic --resource-group pkb05333d87-cassandra_stress0
    az network nic show --output json --name pkb-05333d87-3-nic --resource-group pkb05333d87-cassandra_stress0
    az network nic show --output json --name pkb-05333d87-1-nic --resource-group pkb05333d87-cassandra_stress0
    az vm create --use-unmanaged-disk --location location01 --image Canonical:UbuntuServer:14.04.5-LTS:14.04.201801100 --size Standard_A2 --admin-username perfkit --availability-set pkb05333d87-cassandra_stress0 --storage-sku Standard_LRS --name pkb-05333d87-3 --resource-group pkb05333d87-cassandra_stress0 --nics pkb-05333d87-3-nic --ssh-key-value /tmp/perfkitbenchmarker/runs/05333d87/perfkitbenchmarker_keyfile.pub
    az vm create --use-unmanaged-disk --location location01 --image Canonical:UbuntuServer:14.04.5-LTS:14.04.201801100 --size Standard_A2 --admin-username perfkit --availability-set pkb05333d87-cassandra_stress0 --storage-sku Standard_LRS --name pkb-05333d87-1 --resource-group pkb05333d87-cassandra_stress0 --nics pkb-05333d87-1-nic --ssh-key-value /tmp/perfkitbenchmarker/runs/05333d87/perfkitbenchmarker_keyfile.pub


    The VM pkb-05333d87-3 deploys with success, we see the following returned:

    {
      "fqdns": "",
      "id": "/subscriptions/subnumberremoved/resourceGroups/pkb05333d87-cassandra_stress0/providers/Microsoft.Compute/virtualMachines/pkb-05333d87-3",
      "location": "location01",
      "macAddress": "ABCDEF123",
      "powerState": "VM running",
      "privateIpAddress": "X.X.X.X",
      "publicIpAddress": "X.X.X.X",
      "resourceGroup": "pkb05333d87-cassandra_stress0"
    }

    VM pkb-05333d87-1 however returns:

    Deployment failed. Correlation ID: cd91ceb8-93fd-47be-a00b-b2d96227b581. {
      "status": "Failed",
      "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The resource operation completed with terminal provisioning state 'Failed'.",
        "details": [
          {
            "code": "FabricVmCreationError",
            "message": "Failed to create VM 'pkb-05333d87-1' "
          }
        ]
      }
    }

    Also checking VM pkb-05333d87-1 in the portal, we see the following error message:

    Additional error information is available for this virtual machine:
    GENERAL
    Provisioning state Provisioning failed. Failed to create VM 'pkb-05333d87-1'. FabricVmCreationError
    Guest agent Not Ready. VM agent is not ready
    DISKS
    osdisk_ac34e1e19a Creating.

    Was wondering if anyone out there has encountered this, or able to shed any light?

    To be clear this is being performed on an integrated system, and not ASDK.

    Azure Cli version

    azure-cli (2.0.27)


    • Edited by G2017 Thursday, March 8, 2018 1:33 PM
    Thursday, March 8, 2018 1:16 PM

Answers

All replies

  • To add, I have attempted to enable boot diagnostics on this VM to understand more. The following error is received:

    Failed to update diagnostics settings for pkb-05333d87-3. Extension with publisher 'Microsoft.OSTCExtensions', type 'LinuxDiagnostic', and type handler version '2.3' could not be found in the extension repository.

    Checking the error online I see this issue with AzureStack:

    https://social.msdn.microsoft.com/Forums/SqlServer/en-US/606ea5f0-80e2-4a94-b8be-b5379238857d/microsoftostcextensions-type-linuxdiagnostic-could-not-be-found?forum=AzureStack

    Granted this was Aug 2017, but I assume this is still not addressed. We are currently running on Azure Stack update 1712. 

    I also checked under resource groups>click relevant resource group>deployments>error details it states:

    At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
    Code: (ResourceDeploymentFailure)


    code: (FabricVmCreationError)
    message: "Failed to create VM 'pkb-05333d87-3'"

    Checking the mentioned website I do not see either code 'ResourceDeploymentFailure' and 'FabricVmCreationError', unless I am missing something obvious?


    As mentioned, any light or guidance on troubleshooting this issue would be appreciated.






    • Edited by G2017 Thursday, March 8, 2018 4:54 PM
    Thursday, March 8, 2018 1:56 PM
  • Hello,

    Regarding Linux diagnostics, unfortunately, the Linux Diagnostic Extension is not currently shipped with Azure Stack. This will be available in a future build.  

      

    Let us know how it goes.

                               

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

                 

     Thanks


    Gary Gallanes


    Thursday, March 8, 2018 8:04 PM
  • Hello,

    Can you try redeploying the failed VM and see if you get the same error?

      

    Please let us know how it goes.

                               

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

                 

     Thanks


    Gary Gallanes

    Thursday, March 8, 2018 8:06 PM
  • Hi All,

    Just for clarification, redeploying did not fix anything for us.

    Problem turned out to be the availability set in Azure Stack:

    az vm availability-set create --resource-group pkb05333d87-cassandra_stress0 --name pkb05333d87-cassandra_stress0 --location location01

    Default is 2 Fault Domains which Azure Stack currently does not support.

    Hence he fix for that is to run:

    az vm availability-set create --resource-group pkb05333d87-cassandra_stress0 --name pkb05333d87-cassandra_stress0 --location location01 --platform-fault-domain-count 1 --platform-update-domain-count 1

    Hopefully, that will help someone else :-)

    More info can be found here:
    https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-vm-considerations

    https://docs.microsoft.com/en-us/cli/azure/vm/availability-set?view=azure-cli-latest#az_vm_availability_set_create

    https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/azure-stack/azure-stack-key-features.md<o:p></o:p>


    Monday, March 12, 2018 3:38 PM