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

libcloud azure 400 error on self.driver.get_container() #27

Open
wardi opened this issue Mar 14, 2018 · 3 comments
Open

libcloud azure 400 error on self.driver.get_container() #27

wardi opened this issue Mar 14, 2018 · 3 comments

Comments

@wardi
Copy link

wardi commented Mar 14, 2018

Azure's returning a 400 error due to the header x-ms-version:2012-02-12 on HEAD requests when checking a container name here: https://github.com/TkTech/ckanext-cloudstorage/blob/master/ckanext/cloudstorage/storage.py#L38

Updating libcloud.common.azure.API_VERSION to '2014-02-14' seems to resolve the issue, but it's strange that I have to do this (this change hasn't been made in libcloud's trunk branch)

Do you recommend I hack or monkey patch libcloud 1.5 with this change? Is there a better approach?

@TkTech
Copy link
Owner

TkTech commented Mar 14, 2018

Was the bucket created as a "new"-style Azure bucket or Azure Classic?

@wardi
Copy link
Author

wardi commented Mar 15, 2018

We're using the "new"-style. Are those unsupported by libcloud?

@TkTech
Copy link
Owner

TkTech commented Mar 15, 2018

There doesn't seem to be any official documentation on supported versions, but I ran into a bunch of headaches trying to use the new style buckets for open.canada.ca. Switching to a classic bucket should make your problem disappear if it's an option. Note you can't switch on some of the SEA regional servers.

The proper solution here is to stop using libcloud entirely for Azure and rely on Microsoft's azure package. libcloud's Azure driver doesn't seem to be frequently updated or properly tested.

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

2 participants