-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Regression: az ml job create
fails while uploading code @ v2.17.0
#6294
Comments
Thank you for opening this issue, we will look into it. |
@dionhaefner Apologies for the late reply. Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update. This error occurs when the workspace or registry you are trying to access is not accessible from outside of the designated private link. To resolve this issue, you can try the following steps: Check if your workspace or registry is behind a private endpoint. If it is, you need to create a private endpoint connection to access it. You can follow the steps in the Create a private endpoint connection to Azure Machine Learning article to create a private endpoint connection. If your workspace or registry is not behind a private endpoint, check if you have the necessary permissions to access it. You can check your permissions by going to the Access control (IAM) tab in the Azure portal and checking if you have the necessary roles assigned. If you are using a service principal to authenticate, make sure that it has the necessary permissions to access the workspace or registry. You can check the permissions of your service principal by going to the Access control (IAM) tab in the Azure portal and checking if it has the necessary roles assigned. |
We have double and triple checked all permissions, and everything works fine with v2.16.0. Are there additional permissions required since v2.17.0? |
@dionhaefner I am waiting to hear back from the Product team on this. I will keep you posted. We appreciate your patience. |
@dionhaefner Could you please run the same above CLI command with |
@navba-MSFT It's in the original post ("Additional Context"). |
@dionhaefner My bad. I missed that completely. I will check this further and get back to you. |
@dionhaefner Could you please share the subscription, resource group, workspace name, and timestamps (in UTC) when this happens over email navba [@] microsoft . (dot) com ? |
@dionhaefner I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you had any updates on this. Awaiting your reply. |
I've been on vacation, will send you the info ASAP. |
@dionhaefner Any update on this ? |
It seems that I can't reproduce the issue anymore. Everything works as it should now, both with the most recent az ml extension and I will upgrade our production environment to the most recent version of az ml and see what happens. I'll report back with the requested information if the issue re-surfaces. Thanks for the support @navba-MSFT! |
@dionhaefner Thanks for getting back. We will now proceed with closure of this GitHub issue. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help. |
Describe the bug
Command Name
az ml job create
Extension Name: ml. Version: 2.17.0.
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az ml job create -f {} --set {} --workspace {} --resource-group {} --debug
Expected Behavior
Job gets scheduled successfully, as it does with
az extension add -n ml --version 2.16.0
.Since it works fine with the older version I assume that I actually do have all the necessary permissions.
Environment Summary
Additional Context
👇
Full debug output
The text was updated successfully, but these errors were encountered: