You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/02/03 21:30:37 UTC
[jira] [Commented] (JCLOUDS-178) A 401 error should result in
re-authenticating for a new token
[ https://issues.apache.org/jira/browse/JCLOUDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303919#comment-14303919 ]
ASF GitHub Bot commented on JCLOUDS-178:
----------------------------------------
GitHub user neykov opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/502
Undo #19, fixed upstream
RetryOnRenew fixed in jclouds upstream:
* https://issues.apache.org/jira/browse/JCLOUDS-178
* https://issues.apache.org/jira/browse/JCLOUDS-589
Unit tests are passing, works fine with SL objectstore.
How do I launch the tests in `BlobStoreExpiryTest`? I get `Caused by: java.net.UnknownHostException: keystone-endpoint` at BlobStoreExpiryTest.java:153.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/neykov/incubator-brooklyn undo-pr19
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/502.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #502
----
commit e1451f874d6f3fe9238d8d322ddd4f474226a99f
Author: Svetoslav Neykov <sv...@cloudsoftcorp.com>
Date: 2015-02-03T20:21:17Z
Undo #19, fixed upstream
RetryOnRenew fixed in jclouds upstream:
* https://issues.apache.org/jira/browse/JCLOUDS-178
* https://issues.apache.org/jira/browse/JCLOUDS-589
----
> 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.6.2, 1.7.0
> Reporter: Zack Shoylev
> Assignee: Zack Shoylev
> Fix For: 1.6.3, 1.7.0
>
>
> 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.3.4#6332)