[jira] [Comment Edited] (JCLOUDS-1179) putBlob doesn't handle 401s

["Nick Howes (JIRA)" <ji...@apache.org>]

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

Nick Howes edited comment on JCLOUDS-1179 at 9/15/16 12:14 PM:
---------------------------------------------------------------

Cloned from original issue relating to the old {{swift}} provider - this bug relates to {{2.0.0-SNAPSHOT}} where the problem can still be found in the {{openstack-swift}} provider.


was (Author: nhowes):
Cloned from original issue relating to the old {{swift}} provider - this bug relates to {{2.0.0-SNAPSHOT}} where the problem can still be found.

> 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.7.1, 2.0.0
>         Environment: Devstack on Ubuntu 14.04
>            Reporter: Nick Howes
>              Labels: openstack-swift, 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)