[
https://issues.apache.org/jira/browse/JCLOUDS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082044#comment-14082044
]
Chris Custine commented on JCLOUDS-645:
---------------------------------------
apiVersion isn't even used for the lookup now, it is discarded and null is
passed instead, which causes it to match on any version. So due to the version
mismatch returned from keystone, it is only looking up by region (if
jclouds-region is specified), or returning the last one if none is specified.
You can see the code and comments related to that [here|http://git.io/1q3Yug].
I understand the concern that the behavior changed unintentionally, and of
course it can be changed back if anyone feels it is a blocker for 1.8.0. I
just wanted to make sure it was understood that many factors could influence
this arbitrary endpoint resolution if the client does not specify the region.
For instance, if the cloud provider adds a new region, it could change the
result of first, last, or both, and have the same affect if the client code
does not specify region.
Either way, I will add this to the documentation updates I have pending for the
HP Cloud provider and point out that you need to specify the region, and that
if you don't, the results could be non-deterministic. In the new swift api
provider, you must specify the region when you call getBlobStore or it throws
IllegalArgumentException.
> Incorrect endpoint url chosen for default region of HPCloud Object Storage
> --------------------------------------------------------------------------
>
> Key: JCLOUDS-645
> URL: https://issues.apache.org/jira/browse/JCLOUDS-645
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 1.8.0
> Reporter: Shri Javadekar
> Assignee: Chris Custine
> Fix For: 1.8.0
>
>
> JClouds seems to be choosing the wrong endpoint from the service catalog
> returned by HPCloud Object Storage.
> From what I see there are two endpoints returned in the Object Storage part
> of the service catalog.
> D 07-31 13:21:22.122 pool-1-thread-1 jclouds.wire:59 |::] << "
> "publicURL":
> "https:\/\/region-a.geo-1.objects.hpcloudsvc.com\/v1\/53176293441764",[\n]"
> D 07-31 13:21:22.124 pool-1-thread-1 jclouds.wire:59 |::] << "
> "publicURL":
> "https:\/\/region-b.geo-1.objects.hpcloudsvc.com\/v1\/53176293441764",[\n]"
> I do not have any region configured.
> With 1.7.3, the first url was getting used and my tests were succeeding.
> However, with 1.8.0 the second url get's chosen and my tests failed with a
> "404 Not Found" error.
> See this for more details: http://pastie.org/private/yzxbnvxwidajalcucwflwa
--
This message was sent by Atlassian JIRA
(v6.2#6252)
