jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mat Mannion (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1179) putBlob doesn't handle 401s
Date Wed, 05 Oct 2016 15:46:21 GMT

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

Mat Mannion commented on JCLOUDS-1179:
--------------------------------------

Just to confirm that we see this issue in production even when using the individual jclouds
dependencies

> putBlob doesn't handle 401s 
> ----------------------------
>
>                 Key: JCLOUDS-1179
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1179
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.9.2, 2.0.0
>         Environment: Devstack on Ubuntu 14.04
>            Reporter: Nick Howes
>            Assignee: Zack Shoylev
>              Labels: openstack-swift
>
> After the token used by jclouds expires, subsequent `putBlob` requests to swift fail
with 401.
> Unlike other operations, 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.
> Other operations such as a get _will_ handle a retry by refreshing the auth token, after
which subsequent puts work (until the next expiry)
> Project to reproduce can be found here https://github.com/UniversityofWarwick/jclouds-bug
> 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