jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-589) Port fix for JCLOUDS-178 to non-keystone-v2.0 auth implementations
Date Thu, 06 Nov 2014 15:16:34 GMT

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

ASF GitHub Bot commented on JCLOUDS-589:
----------------------------------------

Github user andreaturli commented on a diff in the pull request:

    https://github.com/apache/incubator-brooklyn/pull/304#discussion_r19949779
  
    --- Diff: locations/jclouds/src/test/java/brooklyn/entity/rebind/persister/jclouds/BlobStoreExpiryTest.java
---
    @@ -151,7 +150,7 @@ protected void doTestRenewAuth(boolean applyFix) throws IOException
{
                 try {
                     assertContainerFound();
                     Assert.fail("should fail as long as "+RetryOnRenew.class+" is not working");
    -            } catch (Exception e) {
    +            } catch (AssertionError e) {
    --- End diff --
    
    @aledsage @ahgittin 
    Looks like there is a fix on that file
    https://issues.apache.org/jira/browse/JCLOUDS-589
    could it be a solution also for 
    https://issues.apache.org/jira/browse/JCLOUDS-615



> Port fix for JCLOUDS-178 to non-keystone-v2.0 auth implementations
> ------------------------------------------------------------------
>
>                 Key: JCLOUDS-589
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-589
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.3
>            Reporter: Shri Javadekar
>            Assignee: Shri Javadekar
>             Fix For: 1.8.0
>
>
> As part of fixing JCLOUDS-178 [1], jclouds added a mechanism for re-authenticating when
it got back a "401 Unauthorized" response. However, this fix only went into the Keystone v2.0
implementation. The problem still exists in the Keystone v1.1 and non-keystone auth implementations.
> This bug should track the porting of that fix to the keystone v1.1 and non-keystone auth
implementations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message