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

Creating ACR registry: throws error Error creating ACR. Please try again later. Response from az was not json: b''. #37

Closed
jazzz308 opened this issue Apr 6, 2017 · 7 comments
Assignees
Labels

Comments

@jazzz308
Copy link

jazzz308 commented Apr 6, 2017

I am trying to create aml environment using DSVM. and when I run aml env setup I get the following error....

Subscription set to Azure Pass
Continue with this subscription (Y/n)? y
Resource group devmlrg already exists, skipping creation.
Registering is still on-going. You can monitor using 'az provider show -n Microsoft.Storage'
Creating storage account devmlstor.
Registering is still on-going. You can monitor using 'az provider show -n Microsoft.ContainerRegistry'
Creating ACR registry: devmlacr (please be patient, this can take several minutes)
Error creating ACR. Please try again later. Response from az was not json: b''.

Any suggestions that would help to resolve the issue??

Thanks

@sajayantony
Copy link
Contributor

Can you please try registering the provider as per https://github.com/Azure/acr/blob/master/docs/Troubleshooting%20Guide.md

@djyou
Copy link
Member

djyou commented Apr 6, 2017

Hi jazzz308,

Error messages in Azure CLI are not always json, this could be by design as error messages are meant to be parsed and read by a human. It looks like you are using AMLBD CLI to create storage account and registry, which however doesn't handle non-json error messages.

I am not seeing any logs to our server side with the registry name devmlacr so I suspect it is a client side error. If you don't have access to the above repo, I can help you raise an issue so that registry creation can be properly handled, but please let me know.

@jazzz308
Copy link
Author

jazzz308 commented Apr 6, 2017

Hi djyou,

I have re-tried with different group devmlcntkacr and got the same result. Do you see any logs relating to that? What sort of logs do i need to see from the client side?

@djyou
Copy link
Member

djyou commented Apr 6, 2017

I have raised an issue against the module you were using and I will keep you posted.

I wasn't sure if you can see any logs but some error messages of why the operation failed will be very helpful. Also I can see that you were creating resources in East US, can you share your region?

@jazzz308
Copy link
Author

jazzz308 commented Apr 6, 2017

Thanks for raising the issue.

My region is Korea Central but when I run aml env setup from putty it somehow installs storage account in US East and throws that error at the end. Do you think the error happens because of the different region it is trying to install ACR?

@djyou
Copy link
Member

djyou commented Apr 21, 2017

Hi jazzz308,

Are you still having the problem? The ML team acknowledged that they have been working on the fix to the issue. One quick way to mitigate the issue is to create the resource group/storage account/container registry in the same region and also have your VM deployed in the same region (or close). I wasn't sure if they are configurable from the module you were using but it is worth trying.

@djyou
Copy link
Member

djyou commented Apr 24, 2017

Closed as this issue has been transferred to amlbdcli team.

@djyou djyou closed this as completed Apr 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants