Closed skylinefly closed 3 years ago
Same error apear under Ubuntu 18.04 LTS with Nodejs v13.9.0 and npm 6.13.7
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. For Linux the file is located _/usr/local/lib/nodemodules/iot-solutions/publish/solutions/remotemonitoring/armtemplates/standard.json
Probably this should keep opened to fix the issue in repository.
HI after fixing the json file another bug occurs deails and how to reproduce see below
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 ✓ 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: "}]}
Type of issue
Description
After psc -t remotemonitoring -s standard -r dotnet and appointing of necessary information the deployment process hungs with SyntaxError right after Application registration. It is always responds with "Unexpected token p in JSON at position 8642".
Steps to reproduce
All done in Power Shell
Expected behavior
Request for VM credentials and normal deployment process flow. RM solution deployment successfully finished
Current behavior <!-- The actual behavior observed --
Application name is registering in AAD - App registrations and process completely hungs up. Termination is possible by ^C.
Known workarounds
...
Possible solution
...
Context and Environment