[Bug / Issue]: Agora Motors
Jumpstart Solution
- [ ] Jumpstart ArcBox
- [ ] Jumpstart LocalBox
- [x] Jumpstart Agora
- [ ] A specific Jumpstart scenario
- [ ] Jumpstart Drops
- [ ] Something else
What happened?
I am deploying Azure Arc Agora Contoso Motors and I notice a few things:
-
main.parameters.json does not include the SSH key as described in the docs and you are prompted during deployment https://github.com/microsoft/azure_arc/blob/main/azure_jumpstart_ag/contoso_motors/bicep/main.parameters.json
-
I get some errors while importing Grafana dashboards in Detroit Environment [1:52 PM] INFO: Importing dashboards for Detroit environment Invoke-RestMethod: { "message": "Not found" } Invoke-RestMethod: { "message": "Not found" }
-
As well as Monterrey, seems like URL may have change [1:54 PM] INFO: Importing dashboards for Monterrey environment Invoke-RestMethod: { "message": "Not found" } Invoke-RestMethod: { "message": "Not found" }
-
I am hitting permission issues not sure what for Code: AuthorizationFailed Message: The client 'xxxx' with object id 'xxxx' does not have authorization to perform action 'Microsoft.Authorization/roleAssignments/write' over scope '/subscriptions/a0d28922-4b2f-43d2-a9eb-4d51ce5b97e0/resourceGroups/Repsol/providers/Microsoft.Storage/storageAccounts/aiostg5d16c/blobServices/default/containers/schemas/providers/Microsoft.Authorization/roleAssignments/xxxx' or the scope is invalid. If access was recently granted, please refresh your credentials. My service principal is owner on the subscription and has the Keyvault required asignments.
-
In the deployment of IoT operations I get errors as well
We need a URL from you
https://jumpstart.azure.com/azure_jumpstart_ag/contoso_motors
Deployment Method
Bicep
Relevant log output.
Invoke-RestMethod: { "message": "Not found" }
Invoke-RestMethod: { "message": "Not found" }
az iot ops create --cluster mycluster -g myresourcegroup --name myinstance --sr-resource-id $SCHEMA_REGISTRY_RESOURCE_ID
Create the target instance with minimum input.
https://aka.ms/cli_ref
Read more about the command in reference docs
argument --sr-resource-id: expected one argument
Examples from AI knowledge base:
az iot ops create --cluster mycluster -g myresourcegroup --name myinstance --sr-resource-id $SCHEMA_REGISTRY_RESOURCE_ID --add-insecure-listener
This example shows deploying an additional insecure (no authn or authz) broker listener configured for port 1883 of service type load balancer. Useful for testing and/or demos. Do not use the insecure option in production.
az iot ops create --cluster mycluster -g myresourcegroup --name myinstance --sr-resource-id $SCHEMA_REGISTRY_RESOURCE_ID --enable-rsync
This form shows how to enable resource sync for the instance deployment. To enable resource sync role assignment write is necessary on the target resource group.
az iot ops create --cluster mycluster -g myresourcegroup --name myinstance --sr-resource-id $SCHEMA_REGISTRY_RESOURCE_ID
Create the target instance with minimum input.
https://aka.ms/cli_ref
Read more about the command in reference docs
[2:05 PM] Error: An error occured while deploying AIO on the cluster...Retrying
Code of Conduct and Licensing
- [x] I agree to follow this project's Code of Conduct and Licensing terms.
Hi @lanicolas! Thanks for reporting this. First, I'll make sure the SSH key gets incorporated into the parameters file. I did a new deployment and also see similar errors; however, the full end-to-end did complete, including the AIO cluster being deployed. I don't see an the AuthorizationFailed error. I'm going to do some more deployments to verify this, update the parameters file, and see what could be causing the errors you saw.
[3:16 PM] INFO: Importing dashboards for Monterrey environment
PS>TerminatingError(Invoke-RestMethod): "
{
"message": "Not found"
}"
Invoke-RestMethod: { "message": "Not found" }
Invoke-RestMethod: { "message": "Not found" }
Mine did deploy in the end but some things were missing like custom location and when you opened data explorer on the VM it was not preconfigured as described in the step by step. So I do think something is failing behind the scenes
Just wanted to provide a follow-up on this: it looks like this error is because of breaking changes that were made starting with Grafana 12.0. Manually reverting to 11.x and trying the Invoke-RestMethod is successful. I'm still sorting out the specific that we need to change but they're broadly described in:
- https://grafana.com/docs/grafana/latest/developers/http_api/apis/
- https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v12-0/
- https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v12-0/#breaking-changes
Note that this also affects Contoso Hypermarket. I'm working on a fix and will provide an update soon.