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

Unable to complete execution of Run promptflow #13

Open
KBaroni opened this issue Oct 27, 2023 · 3 comments
Open

Unable to complete execution of Run promptflow #13

KBaroni opened this issue Oct 27, 2023 · 3 comments

Comments

@KBaroni
Copy link

KBaroni commented Oct 27, 2023

I am following the documentation here: https://learn.microsoft.com/en-us/azure/machine-learning/prompt-flow/how-to-end-to-end-llmops-with-prompt-flow?view=azureml-api-2 and have worked through some initial issues around credentials/secrets and updated variable names in both run.yml and run_evaluation.yml. However, I am stuck with the attached error in the code that appears to run run.yml - and not sure where or how to proceed to debug the issue. If there is a log generated with more details as to where or what the problem is, I was not able to find it.

I reviewed the README.md under the .promptflow folder and am not sure if that could help or where the steps should be executed. If you have any suggestions for how to troubleshoot the issue, please let me know.

Thank you~
Screenshot for LLMOps

@msha1026
Copy link

msha1026 commented Nov 8, 2023

I faced the same issue and was able to fix it by commenting out the runtime: <runtime-name> line in both run_evaluation.yml and run.yml. I believe this fixes it because prompt flow will create a runtime on the fly instead. If you use an existing runtime, the Service Principal that we create in the beginning of the tutorial does not have permission to the underlying compute instance of the runtime. By allowing prompt flow to create a runtime on the fly, the Service Principal should have the correct permissions.

@luoanabecher
Copy link

this won`t solve it for me, have you been able to fix it?

@madiepev
Copy link

madiepev commented Dec 4, 2023

I can confirm that the issue is caused by the runtime. The latest version of the repo sets runtime: automatic. If you leave that as is, instead of changing to your own runtime name, it'll work.

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

No branches or pull requests

4 participants