[JCLOUDS-525] putBlob doesn't handle 401s

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.7.1
• Component/s: jclouds-blobstore
• Labels: swift
• Environment: Keystone + Swift on OpenStack Havana; Ubuntu 12.04
• Assignee: Unassigned
• Reporter: Alex
• Created: 04/Apr/14 16:23
• Updated: 15/Sep/16 12:12
• Resolved: 26/Oct/15 03:43

Description

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.

Issue Links

• is cloned by: JCLOUDS-1179 putBlob doesn't handle 401s