Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing permissions for endpoint to the ml workspace during Deploy Action #7

Open
jakeatmsft opened this issue Sep 18, 2023 · 4 comments · May be fixed by #8
Open

Missing permissions for endpoint to the ml workspace during Deploy Action #7

jakeatmsft opened this issue Sep 18, 2023 · 4 comments · May be fixed by #8
Assignees

Comments

@jakeatmsft
Copy link

Looks like the endpoint needs to be granted permissions before running "Invoke Model" step in Deployment action:

image

Error:
Run az ml online-endpoint invoke --name web-classification-0e1890 --request-file promptflow/deployment/sample-request.json -g *** -w ***
Class WorkspaceHubOperations: This is an experimental class, and may change at any time. Please see https://aka.ms/azuremlexperimental for more information.
ERROR: (UserError) Access denied to list workspace secret due to invalid authentication. Please assign RBAC role 'AzureML Data Scientist' to the endpoint for current workspace, and wait for a few minutes to make sure the new role takes effect. More details can be found in https://aka.ms/pf-runtime.
Code: UserError
Message: Access denied to list workspace secret due to invalid authentication. Please assign RBAC role 'AzureML Data Scientist' to the endpoint for current workspace, and wait for a few minutes to make sure the new role takes effect. More details can be found in https://aka.ms/pf-runtime.

@jakeatmsft jakeatmsft linked a pull request Sep 19, 2023 that will close this issue
@jakeatmsft
Copy link
Author

Opened PR #8 to fix this.

@georgeliang0821
Copy link

@jakeatmsft Has this issue been resolved? I still get the same error here.

@jakeatmsft
Copy link
Author

@jakeatmsft Has this issue been resolved? I still get the same error here.

@georgeliang0821 - PR is still open, please check it out and see if it works for you.

@setuc setuc self-assigned this Oct 18, 2023
@simon-v-swyftx
Copy link

hey @jakeatmsft that PR didn't seem to work for me :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants