libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Grisel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-390) driver.create_container get a 411 error with Azure Blobs driver
Date Tue, 03 Sep 2013 22:47:53 GMT

    [ https://issues.apache.org/jira/browse/LIBCLOUD-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757187#comment-13757187
] 

Olivier Grisel commented on LIBCLOUD-390:
-----------------------------------------

I checked and it correctly inherits from the base class and reuses the `libcloud/common/base.py`'s
`request` method. But as data is None in this case, the fix for LIBCLOUD-362 does not apply
here.
                
> driver.create_container get a 411 error with Azure Blobs driver
> ---------------------------------------------------------------
>
>                 Key: LIBCLOUD-390
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-390
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Storage
>    Affects Versions: 0.12.3
>            Reporter: Olivier Grisel
>
> On current Windows Azure, the Content-Length header is required for container creation
requests. Currently we get the following error:
> {code}
>  [...]
>   File "/Users/ogrisel/code/libcloud/libcloud/storage/drivers/azure_blobs.py", line 499,
in create_container
>     method='PUT', headers=headers)
>   File "/Users/ogrisel/code/libcloud/libcloud/common/base.py", line 617, in request
>     connection=self)
>   File "/Users/ogrisel/code/libcloud/libcloud/common/base.py", line 93, in __init__
>     raise Exception(self.parse_error())
>   File "/Users/ogrisel/code/libcloud/libcloud/common/azure.py", line 74, in parse_error
>     driver=self)
> LibcloudError: <LibcloudError in <libcloud.common.azure.AzureResponse object at
0x10cf8dc90> 'Unknown error Status code: 411.'>
> {code}
> I will soon push a fix in a branch on my github fork.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message