jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-525) putBlob doesn't handle 401s
Date Mon, 26 Oct 2015 03:42:27 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Gaul updated JCLOUDS-525:
--------------------------------

We have removed the legacy "swift" provider.  Please test the modern "openstack-swift" provider
which includes many fixes and enhancements and open a new issue if your problem persists.

> putBlob doesn't handle 401s 
> ----------------------------
>
>                 Key: JCLOUDS-525
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-525
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.1
>         Environment: Keystone + Swift on OpenStack Havana
> Ubuntu 12.04
>            Reporter: Alex
>              Labels: swift
>
> After the token used by jclouds expires, subsequent `putBlob` requests to swift fail
with 401.
> Unlike creations of temporary urls, the `putBlob` command does not resolve this by `POST`ing
to keystone, but instead tries a few times to `PUT` the blob to swift. Each request fails
with a 401 and then it gives up.
> In order to resolve the issue, I must create a temporary url because that responds to
the 401 and creates a new token - which is then stored by jclouds. I can then upload new blobs
until that token has expired (after an hour)
> Output and the script itself can be found here: https://gist.github.com/alexcouper/b8ca68a58a4f39b5e0dc
> It should be noted that when running this script I have altered [token] expiration in
/etc/keystone/keystone.conf to be 2 seconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message