Azure-Samples / iotedge-logging-and-monitoring-solution

IoT Edge Logging and Monitoring Solution (ELMS) is an architecture and sample cloud workflow that enables automated retrieval of logs and metrics from IoT Edge devices
MIT License
42 stars 22 forks source link

re-deployment failed #15

Open ashahbazi58 opened 2 years ago

ashahbazi58 commented 2 years ago

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I deployed the solution as per the instruction for my nested IOT edge environment and I was not able to make the workbook view working so I deleted the resources and tried to redeploy the solution ( used custom option) , but now I'm unable to complete the deployment receiving the role assignment not permitted

Any log messages given by the failure

" Creating resource group deployment. ERROR: {"status":"Failed","error":{"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":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"RoleAssignmentUpdateNotPermitted\",\r\n \"message\": \"Tenant ID, application ID, principal ID, and scope are not allowed to be updated.\"\r\n }\r\n}"},{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"RoleAssignmentUpdateNotPermitted\",\r\n \"message\": \"Tenant ID, application ID, principal ID, and scope are not allowed to be updated.\"\r\n }\r\n}"},{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"RoleAssignmentUpdateNotPermitted\",\r\n \"message\": \"Tenant ID, application ID, principal ID, and scope are not allowed to be updated.\"\r\n }\r\n}"},{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"RoleAssignmentUpdateNotPermitted\",\r\n \"message\": \"Tenant ID, application ID, principal ID, and scope are not allowed to be updated.\"\r\n }\r\n}"}]}}
Something went wrong with the resource group deployment. Ending script. At C:\iotPlatform\IoT-Platform\logging-monitoring\iotedge-logging-and-monitoring-solution\Scripts\deploy.ps1:1012 char:9

  • throw "Something went wrong with the resource group deploymen ...
  • CategoryInfo : OperationStopped: (Something went ... Ending script.:String) [], RuntimeException
  • FullyQualifiedErrorId : Something went wrong with the resource group deployment. Ending script.

    Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?) Powershell

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

marvin-garcia commented 2 years ago

This is related to a recent update that uses managed identities instead of connection strings for IoT Hub and Event Hub. Can you tell me the exact answers you provided to the deployment wizard?

ashahbazi58 commented 2 years ago

Here are the answers I had provided: 1- select the subscription --> same as the 1st deployment 2- choose deployment option: Custom Deployment 3- provide the name of RG--> same as the 1st deployment 4- choose the IoT hub--> same as the 1st deployment ( Use existing IOT Hub) Creating IoT hub shared access policy 'iotedgelogs' with permissions 'RegistryRead ServiceConnect' --> as part of my troubleshooting i deleted the pervious access policy for 'iotedgelogs'

5- Use existing storage account 6-Choose an option from the list for the log analytics workspace (using its index):Use existing log analytics workspace 7- Do you want to enable IoT Edge monitoring? Choose an option from the list (using its Index): Yes 8- How should metrics be uploaded? Choose an option from the list (using its Index):As IoT messages 9- Choose an option from the list for the event hubs namespace (using its index):Use existing event hubs namespace