search

Azure-Samples / graphrag-accelerator

One-click deploy of a Knowledge Graph powered RAG (GraphRAG) in Azure
https://github.com/microsoft/graphrag
MIT License
1.91k stars 315 forks source link

[BUG]Error assigning role to service principal, exiting... #188

Open SridharArrabelly opened 1 month ago

SridharArrabelly commented 1 month ago

Describe the bug I followed the steps as explained in the deployment guide. It appears the provisioning of services has been completed successfully. but the problem with assigning roles after.

To Reproduce Steps to reproduce the behavior:

  1. run bash deploy.sh -p deploy.parameters.json
  2. you will see the error as in the attached screenshot.

Screenshots Screenshot 2024-10-06 164042

Desktop (please complete the following information):

Additional context Resource group and OpenAI are in the same subscription..

timothymeyers commented 1 month ago

@SridharArrabelly - can you verify that your user (or service principal executing the deployment) has the Role Based Access Control (RBAC) Administrator role assigned on your subscription?

I've found this is generally the issue, where this role is either not assigned or is limited in scope to particular resources.

DOliana commented 1 month ago

I had a similar issue - for me restarting the deployment helped. It seems there are some timing issues. Also at some point the issue was that the nodes inthe AKS cluster were still starting.

soon-nl commented 1 month ago

I had a similar issue - for me restarting the deployment helped. It seems there are some timing issues. Also at some point the issue was that the nodes inthe AKS cluster were still starting.

Having the same error. Did you just run bash deploy.sh -p deploy.parameters.json again?

SridharArrabelly commented 1 month ago

@DOliana @soon-nl redploy/run again didn't work. @timothymeyers I can confirm that i have the Role Based Access Control (RBAC) Administrator role. please see attached.

Screenshot 2024-10-09 062044

DOliana commented 1 month ago

I had a similar issue - for me restarting the deployment helped. It seems there are some timing issues. Also at some point the issue was that the nodes inthe AKS cluster were still starting.

Having the same error. Did you just run bash deploy.sh -p deploy.parameters.json again?

yes exactly. rerunning it did the trick for me.