jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zack Shoylev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1179) putBlob doesn't handle 401s
Date Tue, 11 Oct 2016 19:37:20 GMT

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

Zack Shoylev commented on JCLOUDS-1179:


The tests for this were pretty much impossible with our current version of mock web server
(https://github.com/square/okhttp/issues/675), and there were some problems with running a
live test as well. I tested against a separate piece of code, but I added a test that would
work eventually.

This should address this same problem for other providers that use http 1.1 with 100-continue.
This seems to be a somewhat common problem (https://curl.haxx.se/mail/lib-2004-08/0002.html).

> 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

View raw message