locked
Ethereum POA solution template deployment failed - VMExtensionProvisioningError RRS feed

  • Question

  • Hello, 

    I'm following the guide published by Microsoft (https://docs.microsoft.com/en-us/azure/blockchain/templates/ethereum-poa-deployment) on how to deploy the Ethereal POA consortium but I 'm getting a deployment error after some of the components are created (VMs included). I have tried changing regions and other parameters, including passwords, names, size of VMs, etc. but the result is the same.

    The specific error is the following: 

    "code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'config'. Error message: \\\"Enable failed: failed to execute command: command terminated with exit status=5\\n[stdout]\\...

    The last part of the log show the following:

    nConnecting to catalogartifact.azureedge.net (catalogartifact.azureedge.net)|13.107.246.10|:443... connected.\\nHTTP request sent, awaiting response... 200 OK\\nLength: 1652 (1.6K) [application/json]\\nSaving to: ‘backup-poa.sh’\\n\\n 0K . 100% 129M=0s\\n\\n2020-04-15 20:20:53 (129 MB/s) - ‘backup-poa.sh’ saved [1652/1652]\\n\\ndebconf: unable to initialize frontend: Dialog\\ndebconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)\\ndebconf: falling back to frontend: Readline\\ndebconf: unable to initialize frontend: Readline\\ndebconf: (This frontend requires a controlling tty.)\\ndebconf: falling back to frontend: Teletype\\ndpkg-preconfigure: unable to re-open stdin: \\ngpg: requesting key 417A0893 from hkp server packages.microsoft.com\\ngpg: keyserver timed out\\ngpg: keyserver receive failed: keyserver error\\ngpg: requesting key 417A0893 from hkp server packages.microsoft.com\\ngpg: keyserver timed out\\ngpg: keyserver receive failed: keyserver error\\ngpg: requesting key 417A0893 from hkp server packages.microsoft.com\\ngpg: keyserver timed out\\ngpg: keyserver receive failed: keyserver error\\ngpg: requesting key 417A0893 from hkp server packages.microsoft.com\\ngpg: keyserver timed out\\ngpg: keyserver receive failed: keyserver error\\ngpg: requesting key 417A0893 from hkp server packages.microsoft.com\\ngpg: keyserver timed out\\ngpg: keyserver receive failed: keyserver error\\n\\\"

    Is there a workaround? Are there specific parameters that need to be followed? Are there Ethereum POA examples on how to deploy it that can be replicated?

    Thanks. 




    Friday, April 17, 2020 9:32 PM

All replies