[
https://issues.apache.org/jira/browse/JCLOUDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797060#comment-13797060
]
ASF subversion and git services commented on JCLOUDS-178:
---------------------------------------------------------
Commit 7a977b5eaffb411cb3f1409336cdf42f6b46b18c in branch refs/heads/1.6.x from
[~zack-s]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=7a977b5 ]
Reauthenticate on Keystone HTTP 401 (JCLOUDS-178)
The number of retries here is not the same as for 500 errors; expected
behavior is a quick fail while retaining some robustness. This fix
should not reintroduce JCLOUDS-231.
> A 401 error should result in re-authenticating for a new token
> --------------------------------------------------------------
>
> Key: JCLOUDS-178
> URL: https://issues.apache.org/jira/browse/JCLOUDS-178
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.7.0, 1.6.2
> Reporter: Zack Shoylev
> Assignee: Zack Shoylev
> Fix For: 1.7.0, 1.6.3
>
>
> When a keystone service responds with a 401, this means the keystone token
> has expired. Jclouds has to then re-authenticate. Unfortunately, an extra
> condition in the retry was preventing this from happening.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
