Hi @Kentzo, I've downloaded the latest version and run the live tests, but I'm
getting intermittent errors when deserializing the response for the `createTag`
and `createTags` calls. Those tests fail "sometimes" saying something like:
testCreateTags(org.jclouds.cloudsigma2.CloudSigma2LasVegasLiveTest):
Expected BEGIN_OBJECT but was STRING at line 1 column 318
I turned on jclouds wire logging to inspect the request and responses being
generated, and here are the ones generated in the `testCreateTags`:
2013-09-11 00:26:13,402 DEBUG [jclouds.wire] (TestNG) >>
"{"objects":[{"name":"Cloudsigma2 New tag","meta":{}},{"name":"Cloudsigma2 tag
with
resource","meta":{},"resources":["5282fff1-049f-479d-b1fc-faf68341a82d"]}]}"
2013-09-11 00:26:13,403 DEBUG [jclouds.headers] (TestNG) >> POST
https://lvs.cloudsigma.com/api/2.0/tags/ HTTP/1.1
2013-09-11 00:26:13,404 DEBUG [jclouds.headers] (TestNG) >> Accept:
application/json
2013-09-11 00:26:13,404 DEBUG [jclouds.headers] (TestNG) >> Authorization:
Basic bmFjeEBhcGFjaGUub3JnOmpjbDB1ZHMhbDF2Mw==
2013-09-11 00:26:13,405 DEBUG [jclouds.headers] (TestNG) >> Content-Type:
application/json
2013-09-11 00:26:13,405 DEBUG [jclouds.headers] (TestNG) >> Content-Length:
158
2013-09-11 00:26:15,413 DEBUG [jclouds.headers] (TestNG) << HTTP/1.1 201
CREATED
2013-09-11 00:26:15,413 DEBUG [jclouds.headers] (TestNG) <<
Transfer-Encoding: chunked
2013-09-11 00:26:15,414 DEBUG [jclouds.headers] (TestNG) << Date: Tue, 10
Sep 2013 22:26:15 GMT
2013-09-11 00:26:15,414 DEBUG [jclouds.headers] (TestNG) << CF-RAY:
abf89e8427b00de
2013-09-11 00:26:15,415 DEBUG [jclouds.headers] (TestNG) << Location:
https://lvs.cloudsigma.com/api/2.0/tags/
2013-09-11 00:26:15,416 DEBUG [jclouds.headers] (TestNG) << Set-Cookie:
__cfduid=dec16a53d78655bb63249c0d874574f841378851974449; expires=Mon,
23-Dec-2019 23:50:00 GMT; path=/; domain=.cloudsigma.com
2013-09-11 00:26:15,416 DEBUG [jclouds.headers] (TestNG) << Connection:
keep-alive
2013-09-11 00:26:15,417 DEBUG [jclouds.headers] (TestNG) << Server:
cloudflare-nginx
2013-09-11 00:26:15,417 DEBUG [jclouds.headers] (TestNG) << X-API-Version:
Nitrogen.prod.1837e2d48570+
2013-09-11 00:26:15,418 DEBUG [jclouds.headers] (TestNG) << Content-Type:
application/json; charset=utf-8
2013-09-11 00:26:15,420 DEBUG [jclouds.wire] (TestNG) << "{"objects":
[{"meta": {}, "name": "Cloudsigma2 New tag", "resource_uri":
"/api/2.0/tags/9e9697fc-3670-4ec9-8166-1c429f0d6b3c/", "uuid":
"9e9697fc-3670-4ec9-8166-1c429f0d6b3c"}, {"meta": {}, "name": "Cloudsigma2 tag
with resource", "resource_uri":
"/api/2.0/tags/7825e6cb-3f4b-4894-9e90-18d26ee25a4c/", "resources":
["5282fff1-049f-479d-b1fc-faf68341a82d"], "uuid":
"7825e6cb-3f4b-4894-9e90-18d26ee25a4c"}]}"
If you take a look at the returned json, it seems that the problem is in the
`resources` list. When deserializing the list of `Tag` objects, jclouds expects
it to have a list of `TagResource` objects, but the json returned by the api
has instead a list of strings (just the uuid of the resource).
I don't quite understand why this only happens sometimes. Could it be a
server-side issue, or is it something that should be fixed in the provider code?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/12#issuecomment-24200766
