Azure / pcs-cli

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

RemoteMonitoring standard deployment failed #535

Closed baranyiszabolcs closed 3 years ago

baranyiszabolcs commented 4 years ago

Type of issue

Description

HI after fixing the json file another bug occurs deails and how to reproduce see below

✓ Application registered: https://portal.azure.com/microsoft.onmicrosoft.com#blade/Microsoft_AAD_IAM/ApplicationBlade/o✓ Created resource group: https://portal.azure.com/microsoft.onmicrosoft.com#resource/subscriptions/4a99ad0b-5a1c-46f4-✕ Deployment validation failed: { "code": "InvalidTemplateDeployment", "message": "The template deployment 'deployment-bszrmonky' is not valid according to the validation procedure. The tracking id is '33d3d3d1-f0a9-4f42-81ea-4de75613bd02'. See inner errors for details.", "details": [ { "code": "ServicePrincipalNotFound", "message": "Provisioning of resource(s) for container service bszrmonky-cluster in resource group bszrmonky failed. Message: {\n \"code\": \"ServicePrincipalNotFound\",\n \"message\": \"Service principal clientID: e9ff31a2-dd9f-41✕ Error: {"code":"InvalidTemplateDeployment","message":"The template deployment 'deployment-bszrmonky' is not valid according to the validation procedure. The tracking id is '33d3d3d1-f0a9-4f42-81ea-4de75613bd02'. See inner errors for details.","details":[{"code":"ServicePrincipalNotFound","message":"Provisioning of resource(s) for container service bszrmonky-cluster in resource group bszrmonky failed. Message: {\n \"code\": \"ServicePrincipalNotFound\",\n \"message\": \"Service principal clientID: e9ff31a2-dd9f-41dc-b0de-cdb32472afef not found in Active Directory tenant 72f988bf-86f1-41af-91ab-2d7cd011db47, Please see https://aka.ms/aks-sp-help for more details.\"\n }. Details: "}]}

Steps to reproduce

1.. FIx the standard json file: So, to fix the problem described you need to make some changes in file pcs-cli/publish/solutions/remotemonitoring/armtemplates/standard.json In 240 string there is "pcs" statment that is typo mistake. Just delete it and save the file. After that you will able to proceed with deployment as well.

Run cli like this: C:\tmp>pcs -t remotemonitoring -s standard -r dotnet ? Enter a solution name: bszrmonky ? Select a subscription: Microsoft Azure Internal Consumption ? Select a location: North Europe ? Enter prefix for .azurewebsites.net: bszrmonky

  1. [Second step]
  2. [and so on...]

Expected behavior

Script contnues and create the deploymnet

Current behavior <!-- The actual behavior observed --

...

Known workarounds

...

Possible solution

...

Context and Environment