Azure / pcs-cli

A CLI for deploying Azure IoT PCS
MIT License
33 stars 37 forks source link

KeyVault Conflict When Deploying Remote Monitoring basic via the CLI #517

Closed zhshen closed 3 years ago

zhshen commented 5 years ago

Type of issue

Description

When I was deploying resource monitoring, the deployments of resources group raised an error. 'VM has reported a failure when processing extension 'scriptextensions''.

Steps to reproduce

  1. npm install
  2. npm start
  3. npm link
  4. pcs login
  5. pcs

    Current behavior

    For a long time, the deployment stopped and show an error message:

At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.

I checked the deployment log in resource group. I found the keyvault deployment showed an exception when it was trying to deploy the vm-xxxx/scriptextensions :

"statusCode": "Conflict", "statusMessage": { "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'scriptextensions'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=1\n[stdout]\nExit code: 1\nSetup failed, please see log file '/app/setup.log' for more information\n\n[stderr]\n\"." } ] } },.

Expected behavior

I tried East Asia and West US with difference subscriptions, this error has still been occurred.

Known workarounds

If I remove the Microsoft.Compute/virtualMachines/extensions in keyvault.json. The deployment would be continued.

Possible solution

...

Context and Environment

Ashurek85 commented 5 years ago

I have the same issue.

You said that "if I remove the Microsoft.Compute/virtualMachines/extensions in keyvault.json. The deployment would be continued."

The system works? Can I execute extensions manually?

zhshen commented 5 years ago

No, The system can not work after I remove the 'Microsoft.Compute/virtualMachines/extensions'

Ashurek85 commented 5 years ago

This is a serious problem, we need a solution

Ashurek85 commented 5 years ago

Detail error:

image

ravitola commented 5 years ago

I am having a similar issue. Is there a workaround or is fix underway to resolve this issue ?

elvinm commented 5 years ago

I am currently not seeing this issue. I was able to install with npm instlal -g iot-solutions and then deploy with pcs. The website was running right after. Do you have any further details on how you reproduced this yesterday?

Ashurek85 commented 5 years ago

Steps:

  1. From command line -> npm install -g iot-solutions
  2. With VS Code -> Debug -> pcs basic dotnet
  3. Enter parameters in VS Code terminal.
  4. Ten minutes later i get this error: image

image

The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'scriptextensions'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=1\n[stdout]\nExit code: 1\nSetup failed, please see log file '/app/setup.log' for more information\n\n[stderr]\n\"." }]

LSpencer777 commented 4 years ago

I get exactly the same error as @Ashurek85

Microsoft, why are you apparently not paying attention to this issue? It has been open for almost a year. Users (like me) who want to evaluate your Azure IoT solution are going to get frustrated and go elsewhere.

muralim2576 commented 4 years ago

What a pathetic way of managing things by Microsoft. This issue has been around for years, is this how Microsoft provides support for their solutions??