[
https://issues.apache.org/jira/browse/JCLOUDS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081941#comment-14081941
]
Shri Javadekar commented on JCLOUDS-645:
----------------------------------------
Do you know what commit changed the default apiVersion from 1.0 to null? Also,
do we know what are the other repercussions of this change? What happens if I
set the region as "region-a.geo-1" but set the api version to "1" (and not
"1.0")?
Would smiply explicitly setting the apiVersion to "1.0" be a workaround? I
tried doing that but don't see any change in the behavior. "region-b" continues
to get selected instead of "region-a".
The behavior of the system may not have been explicitly defined earlier and I
agree downstream code ideally should not depend on this. However, changing the
behavior of the system without prior notice and adequate time for action
doesn't seem like the best approach to me.
> 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)
