jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1179) putBlob doesn't handle 401s
Date Thu, 13 Oct 2016 17:18:20 GMT

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

ASF subversion and git services commented on JCLOUDS-1179:
----------------------------------------------------------

Commit 00f7ee0738fb855119ab048a40832efe97bc6335 in jclouds's branch refs/heads/master from
[~zack-s]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=00f7ee0 ]

jclouds was not properly retrying on an expect: 100-continue PUT request that requires re-athentication
because of java protocol code

JCLOUDS-1179 This fix also addresses the same problem with other providers

No currently working tests because of https://github.com/square/okhttp/issues/675

This is a common problem in other tools as well 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
>             Fix For: 2.0.0
>
>
> 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