Bug in Jclouds

[Swetha Somula]

Hi,

I am trying to invoke Nova API from Jclouds.
I am getting the response as

- Http: Response, HTTP/1.1, Status: No content, URL: /v1.1
StatusCode: 204, No content
X-Server-Management-Url: http://dragon004/v1.1
X-Storage-Url:
X-Cdn-Management-Url:

As per the below link, they are syaing its a bug in Jclouds.
https://bugs.launchpad.net/nova/+bug/761014

Can you people please confirm this?
If so which version of Jclouds has a fix for this.
I am using 1.5.alpha.1 version.

Thanks

[Adrian Cole]

Hi, Swetha.

Accommodating this is easy, basically add @VirtualHost to
org.jclouds.openstack.keystone.v1_1.AuthenticationAsyncClient

Can you add this to here:

http://code.google.com/p/jclouds/issues

-A

> --
> You received this message because you are subscribed to the Google Groups "jclouds" group.
> To post to this group, send email to jcl...@googlegroups.com.
> To unsubscribe from this group, send email to jclouds+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/jclouds?hl=en.
>

[Swetha Somula]

Hi,

If i use curl commands, the openstack is returning with port number.
So i came to an understanding taht this a bug in Jclouds.
Can you tell me what exactly i should be doing to fix this bug?
Because when i look into my code i am not at all using the jar which
involves the class you are specifying.

Thanks u.

[Adrian Cole]

Hi, Swetha.

Great job on the issue. It had every detail I needed!

So, what happened was that our default http driver uses
HttpURLConnection to send requests. Eventhough we don't specify a
Host header in our code, there's an implicit one added, which doesn't
have the port. The fix is for us to explicitly add the Host header
that has the port. I'm testing this now.

Cheers,
-A

[Adrian Cole]

sorted in 1.5.0-SNAPSHOT, and will be in 1.5.0-beta.2 when we release that.

-A

[Swetha Somula]

Hi Adrian,
Thanks for the fix.

I have tried with 1.5.0-SNAPSHOT.
But i got the same result.
Only difference is now an extra header HOST is being passed, but the X-
Server-Management-Url being sent back didn't change.
Still the port number is not seen when the request is sent to
openstack.
Please find the Jclods log.

[main] INFO bug.Bug - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
0 [main] DEBUG jclouds.compute - >> listing nodes
63 [main] DEBUG org.jclouds.rest.internal.AsyncRestClientProxy -
Invoking OpenStackAuthAsyncClient.authenticate
63 [i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService - Sending
request -1451508936: GET http://198.55.32.96:8774/v1.1 HTTP/1.1
63 [i/o thread 0] DEBUG jclouds.headers - >> GET http://198.55.32.96:8774/v1.1
HTTP/1.1
63 [i/o thread 0] DEBUG jclouds.headers - >> X-Auth-User: admin
63 [i/o thread 0] DEBUG jclouds.headers - >> X-Auth-Key:
971090f3-6492-470d-a477-000a24678eb3
63 [i/o thread 0] DEBUG jclouds.headers - >> Accept: */*
63 [i/o thread 0] DEBUG jclouds.headers - >> Host:
198.55.32.96:8774
875 [i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService -
Receiving response -1451508936: HTTP/1.1 204 No Content
875 [i/o thread 0] DEBUG jclouds.headers - << HTTP/1.1 204 No
Content
875 [i/o thread 0] DEBUG jclouds.headers - << Date: Mon, 28 May 2012
03:49:04 GMT
875 [i/o thread 0] DEBUG jclouds.headers - << X-Storage-Url:
875 [i/o thread 0] DEBUG jclouds.headers - << X-Server-Management-
Url: http://198.55.32.96/v1.1/inp
875 [i/o thread 0] DEBUG jclouds.headers - << X-Auth-Token:
bdbf7755fd84bef877af5ce18d31939bae31e9c9
875 [i/o thread 0] DEBUG jclouds.headers - << X-Cdn-Management-Url:
875 [i/o thread 0] DEBUG jclouds.headers - << Connection: keep-alive
891 [user thread 1] DEBUG
org.jclouds.openstack.functions.ParseAuthenticationResponseFromHeaders
- will connect to:
907 [main] DEBUG org.jclouds.rest.internal.AsyncRestClientProxy -
Invoking NovaAsyncClient.listServers
907 [i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService - Sending
request -1804928114: GET http://198.55.32.96/v1.1/inp/servers/detail?format=json&now=1338176902578
HTTP/1.1
907 [i/o thread 0] DEBUG jclouds.headers - >> GET
http://198.55.32.96/v1.1/inp/servers/detail?format=json&now=1338176902578
HTTP/1.1
907 [i/o thread 0] DEBUG jclouds.headers - >> Accept: application/
json
907 [i/o thread 0] DEBUG jclouds.headers - >> X-Auth-Token:
bdbf7755fd84bef877af5ce18d31939bae31e9c9
4672 [i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService -
Receiving response -1804928114: HTTP/1.1 404 Not Found
4672 [i/o thread 0] DEBUG jclouds.headers - << HTTP/1.1 404 Not Found
4672 [i/o thread 0] DEBUG jclouds.headers - << Date: Mon, 28 May 2012
03:49:05 GMT
4672 [i/o thread 0] DEBUG jclouds.headers - << Vary: Accept-Encoding
4672 [i/o thread 0] DEBUG jclouds.headers - << Keep-Alive:
timeout=15, max=100
4688 [i/o thread 0] DEBUG jclouds.headers - << Connection: Keep-Alive
4688 [i/o thread 0] DEBUG jclouds.headers - << Server: Apache/2.2.14
(Ubuntu)
4688 [i/o thread 0] DEBUG jclouds.headers - << Content-Type: text/
html; charset=iso-8859-1
4688 [i/o thread 0] DEBUG jclouds.headers - << Content-Length: 299
4688 [i/o thread 0] DEBUG jclouds.wire - << "<!DOCTYPE HTML PUBLIC
"-//IETF//DTD HTML 2.0//EN">[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "<html><head>[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "<title>404 Not Found</
title>[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "</head><body>[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "<h1>Not Found</h1>[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "<p>The requested URL /
v1.1/inp/servers/detail was not found on this server.</p>[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "<hr>[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "<address>Apache/2.2.14
(Ubuntu) Server at 198.55.32.96 Port 80</address>[\n]"
4688 [i/o thread 0] DEBUG jclouds.wire - << "</body></html>[\n]"
4688 [main] DEBUG jclouds.compute - << list(0)
4688 [main] INFO bug.Bug - [] dfdfdf
4688 [main] INFO bug.Bug -

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
On May 26, 10:29 am, Adrian Cole <adrian.f.c...@gmail.com> wrote:
> sorted in 1.5.0-SNAPSHOT, and will be in 1.5.0-beta.2 when we release that.
>
> -A
>
>
>
>
>
>
>
> On Fri, May 25, 2012 at 9:57 PM, Adrian Cole <adrian.f.c...@gmail.com> wrote:
> > Hi, Swetha.
>
> > Great job on the issue.  It had every detail I needed!
>
> > So, what happened was that our default http driver uses
> > HttpURLConnection to send requests.  Eventhough we don't specify a
> > Host header in our code, there's an implicit one added, which doesn't
> > have the port.  The fix is for us to explicitly add the Host header
> > that has the port.  I'm testing this now.
>
> > Cheers,
> > -A
>

[Adrian Cole]

Hi, Swetha.

Sorry you are having trouble.  In your log, jclouds sets the correct Host header, yet the server responds with a management url minus a port number.  If this is unexpected, you probably want to contact your server team.

While Diablo is the minimum version jclouds can support, you are experiencing struggles others who are current with OpenStack+ Keystone don't. Unsolicited advice is to not only to another old version, but rather update to Essex, which many folks I know say is 'years ahead in instability' over Diablo. 

Anyway, good luck with debugging the server response that is sending back an incorrect url.

-A

[Adrian Cole]

p.s. I was wrong.. we do incorrectly specify the Host header in the
default http impl!!

http://code.google.com/p/jclouds/issues/detail?id=953

Fixing the above, we should be able to rollback the workaround which
added @VirtualHost to apis/nova/...NovaAsyncClient.java

On May 25, 9:57 pm, Adrian Cole <adrian.f.c...@gmail.com> wrote:
> Hi, Swetha.
>

> Great job on the issue.  It had every detail I needed!
>
> So, what happened was that our default http driver uses

> HttpURLConnection to send requests.  Eventhough we don't specify aHostheaderin our code, there's an implicit one added, which doesn't

[Vijay Kiran]

Hi Swetha,

The fix for 953 issue has just been applied, can you try the next snapshot and let us know if it fixes the your problem ?

./Vijay

> >> > To unsubscribe from this group, send email to jclouds+unsubscribe@googlegroups.com.

> >> > For more options, visit this group athttp://groups.google.com/group/jclouds?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups "jclouds" group.
> > To post to this group, send email to jcl...@googlegroups.com.

> > To unsubscribe from this group, send email to jclouds+unsubscribe@googlegroups.com.

[Swetha Somula]

Hi Vijay,
Can you be more specific on next snapshot?
you mean version 1.5.0-SNAPSHOT?

-Swetha Somula.

> > jclouds+u...@googlegroups.com.

> > > >> > For more options, visit this group athttp://
> > groups.google.com/group/jclouds?hl=en.
>

> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups "jclouds" group.
> > > > To post to this group, send email to jcl...@googlegroups.com.
> > > > To unsubscribe from this group, send email to

> > jclouds+u...@googlegroups.com.

[Vijay Kiran]

Hi Swetha,

Yes, I meant the latest snapshot -  which is indeed 1.5.0-SNAPSHOT

Seems like the latest one is built on 4th June (https://oss.sonatype.org/content/repositories/snapshots/org/jclouds/).

./Vijay.

> > jclouds+unsubscribe@googlegroups.com.

> > > >> > For more options, visit this group athttp://
> > groups.google.com/group/jclouds?hl=en.
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups "jclouds" group.
> > > > To post to this group, send email to jcl...@googlegroups.com.
> > > > To unsubscribe from this group, send email to

> > jclouds+unsubscribe@googlegroups.com.

[Swetha Somula]

Thnak u Vijay.
I will try it out.

> > > > jclouds+u...@googlegroups.com.

> > > > > >> > For more options, visit this group athttp://
> > > > groups.google.com/group/jclouds?hl=en.
>
> > > > > > --
> > > > > > You received this message because you are subscribed to the Google
> > > > Groups "jclouds" group.
> > > > > > To post to this group, send email to jcl...@googlegroups.com.
> > > > > > To unsubscribe from this group, send email to

> > > > jclouds+u...@googlegroups.com.

[Swetha Somula]

Hi,

I am still getting the Service-Management url with out the port after
using the fix also.
Please see the log.


0 [main] INFO bug.Bug -

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
0 [main] DEBUG jclouds.compute - >> listing nodes

62 [main] DEBUG org.jclouds.rest.internal.AsyncRestClientProxy -
Invoking OpenStackAuthAsyncClient.authenticate
62 [i/o thread 0] DEBUG

org.jclouds.http.internal.JavaUrlHttpCommandExecutorService - Sending
request -1451508936: GET http://198.55.32.96:8774/v1.1 HTTP/1.1

62 [i/o thread 0] DEBUG jclouds.headers - >> GET http://198.55.32.96:8774/v1.1
HTTP/1.1
62 [i/o thread 0] DEBUG jclouds.headers - >> X-Auth-User: admin
62 [i/o thread 0] DEBUG jclouds.headers - >> X-Auth-Key:
971090f3-6492-470d-a477-000a24678eb3
62 [i/o thread 0] DEBUG jclouds.headers - >> Accept: */*
62 [i/o thread 0] DEBUG jclouds.headers - >> Host:
198.55.32.96:8774
1625 [i/o thread 0] DEBUG

org.jclouds.http.internal.JavaUrlHttpCommandExecutorService -
Receiving response -1451508936: HTTP/1.1 204 No Content

1640 [i/o thread 0] DEBUG jclouds.headers - << HTTP/1.1 204 No
Content
1640 [i/o thread 0] DEBUG jclouds.headers - << Date: Tue, 05 Jun 2012
09:22:16 GMT
1640 [i/o thread 0] DEBUG jclouds.headers - << X-Storage-Url:
1640 [i/o thread 0] DEBUG jclouds.headers - << X-Server-Management-
Url: http://198.55.32.96/v1.1/inp
1640 [i/o thread 0] DEBUG jclouds.headers - << X-Auth-Token:
91e4a26f0bdd27ca386ece599a076891b3e44602
1640 [i/o thread 0] DEBUG jclouds.headers - << X-Cdn-Management-Url:
1640 [i/o thread 0] DEBUG jclouds.headers - << Connection: keep-alive
1640 [user thread 1] DEBUG

org.jclouds.openstack.functions.ParseAuthenticationResponseFromHeaders
- will connect to:

1687 [main] DEBUG org.jclouds.rest.internal.AsyncRestClientProxy -
Invoking NovaAsyncClient.listServers
1687 [i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService - Sending
request 797476096: GET http://198.55.32.96/v1.1/inp/servers/detail?format=json&now=1338888093312
HTTP/1.1
1687 [i/o thread 0] DEBUG jclouds.headers - >> GET
http://198.55.32.96/v1.1/inp/servers/detail?format=json&now=1338888093312
HTTP/1.1
1687 [i/o thread 0] DEBUG jclouds.headers - >> Accept: application/
json
1687 [i/o thread 0] DEBUG jclouds.headers - >> X-Auth-Token:
91e4a26f0bdd27ca386ece599a076891b3e44602
3171 [i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService -
Receiving response 797476096: HTTP/1.1 404 Not Found
3171 [i/o thread 0] DEBUG jclouds.headers - << HTTP/1.1 404 Not Found
3171 [i/o thread 0] DEBUG jclouds.headers - << Date: Tue, 05 Jun 2012
09:22:17 GMT
3171 [i/o thread 0] DEBUG jclouds.headers - << Vary: Accept-Encoding
3171 [i/o thread 0] DEBUG jclouds.headers - << Keep-Alive:
timeout=15, max=100
3171 [i/o thread 0] DEBUG jclouds.headers - << Connection: Keep-Alive
3171 [i/o thread 0] DEBUG jclouds.headers - << Server: Apache/2.2.14
(Ubuntu)
3171 [i/o thread 0] DEBUG jclouds.headers - << Content-Type: text/
html; charset=iso-8859-1
3171 [i/o thread 0] DEBUG jclouds.headers - << Content-Length: 299
3171 [i/o thread 0] DEBUG jclouds.wire - << "<!DOCTYPE HTML PUBLIC
"-//IETF//DTD HTML 2.0//EN">[\n]"
3171 [i/o thread 0] DEBUG jclouds.wire - << "<html><head>[\n]"
3171 [i/o thread 0] DEBUG jclouds.wire - << "<title>404 Not Found</
title>[\n]"
3171 [i/o thread 0] DEBUG jclouds.wire - << "</head><body>[\n]"
3171 [i/o thread 0] DEBUG jclouds.wire - << "<h1>Not Found</h1>[\n]"
3171 [i/o thread 0] DEBUG jclouds.wire - << "<p>The requested URL /

v1.1/inp/servers/detail was not found on this server.</p>[\n]"

3171 [i/o thread 0] DEBUG jclouds.wire - << "<hr>[\n]"
3171 [i/o thread 0] DEBUG jclouds.wire - << "<address>Apache/2.2.14

(Ubuntu) Server at 198.55.32.96 Port 80</address>[\n]"

3171 [i/o thread 0] DEBUG jclouds.wire - << "</body></html>[\n]"
3187 [main] DEBUG jclouds.compute - << list(0)
3187 [main] INFO bug.Bug - [] dfdfdf
3187 [main] INFO bug.Bug -
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

[Vijay Kiran]

Hi Swetha,

X-Server-Management- Url: http://198.55.32.96/v1.1/inp 

Looks like the jclouds is sending the request to the correct management URL as returned after the first request. Are you sure that the headers returned by the server are correct (esp. Server-Management-Url ?)

/.Vijay

[Swetha Somula]

That is what my concern from beginning.

When i tried with curl, the header response i receive from openstack
has port number in the URL.
But when i request with Jclouds, the header response doesn't has the
port number in URL.
So i am not able to understand whether its the problem of Jclouds or
is it problem with openstack.
If problem is with openstack then, even the response returned to curl
request should not contain the port, but its not the case.
so what do you suggest?

On Jun 5, 2:57 pm, Vijay Kiran <m...@vijaykiran.com> wrote:
> Hi Swetha,
>
> X-Server-Management- Url:http://198.55.32.96/v1.1/inp
>
> Looks like the jclouds is sending the request to the correct management URL
> as returned after the first request. Are you sure that the headers returned
> by the server are correct (esp. Server-Management-Url ?)
>
> /.Vijay
>
>
>
>
>
>
>
> On Tuesday, June 5, 2012 11:27:57 AM UTC+2, Swetha Somula wrote:
>
> > Hi,
>
> > I am still getting the Service-Management url with out the port after
> > using the fix also.
> > Please see the log.
>
> > 0    [main] INFO  bug.Bug  -
>
> > 0    [main] DEBUG jclouds.compute  - >> listing nodes
> > 62   [main] DEBUG org.jclouds.rest.internal.AsyncRestClientProxy  -
> > Invoking OpenStackAuthAsyncClient.authenticate
> > 62   [i/o thread 0] DEBUG
> > org.jclouds.http.internal.JavaUrlHttpCommandExecutorService  - Sending
> > request -1451508936: GEThttp://198.55.32.96:8774/v1.1HTTP/1.1
> > 62   [i/o thread 0] DEBUG jclouds.headers  - >> GEThttp://198.55.32.96:8774/v1.1
>

> > HTTP/1.1 <http://198.55.32.96:8774/v1.1HTTP/1.1>

> > request 797476096: GEThttp://198.55.32.96/v1.1/inp/servers/detail?format=json&now=133888809...
>
> > HTTP/1.1<http://198.55.32.96/v1.1/inp/servers/detail?format=json&now=133888809...>

> > 1687 [i/o thread 0] DEBUG jclouds.headers  - >> GET

> >http://198.55.32.96/v1.1/inp/servers/detail?format=json&now=133888809...
> > HTTP/1.1<http://198.55.32.96/v1.1/inp/servers/detail?format=json&now=133888809...>

[Vijay Kiran]

Hi Swetha,

Sorry, I seem to have misunderstood your problem.

If curl is working fine but not JClouds, then clearly it is a problem with parsing the response in JClouds- which means the fix I made isn't working or in the wrong place to begin with.

After a quick look, I'm guessing that the port is lost here: https://github.com/jclouds/jclouds/blob/master/common/openstack/src/main/java/org/jclouds/openstack/functions/ParseAuthenticationResponseFromHeaders.java#L81

I'll test the fix and let you know ASAP.

./Vijay

[Adrian Cole]

motion to use Keystone?

We don't have any test endpoints running the old version of diablo you
are running anymore. I suggest you motion your powers to update to
Essex/Keystone, as troubleshooting an old version of diablo is tedious
and not very reusable as folks transition to Essex+.

You can also consider using our "eucalyptus" api against the old
version of Nova you are running. Many have found this more reliable.

-A

> --
> You received this message because you are subscribed to the Google Groups
> "jclouds" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/jclouds/-/_2FThCUoqToJ.

[Adrian Cole]

P.S.

It is possible to use Keystone Essex against Nova Diablo. For
example, hpcloud-compute has this setup. This pattern can help you
transition towards Essex without ripping out your Diablo install, and
simultaneously avoid the problems you are encountering.

I hope it helps,
-A

[Swetha Somula]

In order to use eucaluptus api what are the prerequisites i should
have in my openstack?

because if i am requesting for http://hostname:8773/services/eucalyptus/
from the browser i am getting some values as

1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01
2008-09-01 2009-04-04

Even if i use Jclouds the reply is same and an exception as

[i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService - Sending

request 301850041: POST http://hostname:8773/services/eucalyptus/ HTTP/
1.1
407 [i/o thread 0] DEBUG jclouds.wire - >>
"Action=DescribeRegions&Signature=WB3MaPlh
%2FDlkvQAyEJ8fX9MiFicJyLEqv3c2ASDGR%2FM
%3D&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-06T05%3A11%3A52.234Z&Version=2010-06-15&AWSAccessKeyId=aaaaaaaaa971090f3-6492-470d-
a477-000a24678eb3"
407 [i/o thread 0] DEBUG jclouds.headers - >> POST
http://hostname:8773/services/eucalyptus/ HTTP/1.1
407 [i/o thread 0] DEBUG jclouds.headers - >> Host: hostname:8773
407 [i/o thread 0] DEBUG jclouds.headers - >> Content-Type:
application/x-www-form-urlencoded
407 [i/o thread 0] DEBUG jclouds.headers - >> Content-Length: 248
1203 [i/o thread 0] DEBUG
org.jclouds.http.internal.JavaUrlHttpCommandExecutorService -
Receiving response 301850041: HTTP/1.1 200 OK
1203 [i/o thread 0] DEBUG jclouds.headers - << HTTP/1.1 200 OK
1203 [i/o thread 0] DEBUG jclouds.headers - << Date: Wed, 06 Jun 2012
05:11:37 GMT
1203 [i/o thread 0] DEBUG jclouds.headers - << Connection: keep-alive
1203 [i/o thread 0] DEBUG jclouds.headers - << Content-Type: text/
html; charset=UTF-8
1203 [i/o thread 0] DEBUG jclouds.headers - << Content-Length: 92
1203 [i/o thread 0] DEBUG jclouds.wire - << "1.0[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2007-01-19[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2007-03-01[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2007-08-29[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2007-10-10[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2007-12-15[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2008-02-01[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2008-09-01[\n]"
1203 [i/o thread 0] DEBUG jclouds.wire - << "2009-04-04[\n]"
1250 [user thread 1] ERROR jclouds.compute - amis, completed: 0/1,
errors: 1, rate: 0ms/op
java.util.concurrent.ExecutionException: java.lang.RuntimeException:
request: POST http://hostname:8773/services/eucalyptus/ HTTP/1.1;
error at 1:1 in document ; cause: org.xml.sax.SAXParseException:
Content is not allowed in prolog.
at com.google.common.util.concurrent.AbstractFuture
$Sync.getValue(AbstractFuture.java:289)
at com.google.common.util.concurrent.AbstractFuture
$Sync.get(AbstractFuture.java:276)
at
com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:
111)
at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:
134)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException: request: POST
http://hostname:8773/services/eucalyptus/ HTTP/1.1; error at 1:1 in
document ; cause: org.xml.sax.SAXParseException: Content is not
allowed in prolog.
at
org.jclouds.http.functions.ParseSax.addDetailsAndPropagate(ParseSax.java:
174)
at
org.jclouds.http.functions.ParseSax.addDetailsAndPropagate(ParseSax.java:
146)
at org.jclouds.http.functions.ParseSax.parse(ParseSax.java:132)
at org.jclouds.http.functions.ParseSax.apply(ParseSax.java:86)
at org.jclouds.http.functions.ParseSax.apply(ParseSax.java:54)
at com.google.common.util.concurrent.Futures$3.apply(Futures.java:
380)
at com.google.common.util.concurrent.Futures
$ChainingListenableFuture.run(Futures.java:522)
... 3 more
Caused by: org.xml.sax.SAXParseException: Content is not allowed in
prolog.
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:
1231)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl
$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.jclouds.http.functions.ParseSax.doParse(ParseSax.java:141)
at org.jclouds.http.functions.ParseSax.parse(ParseSax.java:130)
... 7 more
1250 [main] ERROR jclouds.compute - amis, completed: 0/1, errors: 1,
rate: 0ms/op
java.lang.RuntimeException: amis, completed: 0/1, errors: 1, rate: 0ms/
op
at
org.jclouds.concurrent.FutureIterables.awaitCompletion(FutureIterables.java:
157)
at
org.jclouds.concurrent.FutureIterables.transformParallel(FutureIterables.java:
101)
at
org.jclouds.concurrent.FutureIterables.transformParallel(FutureIterables.java:
86)
at
org.jclouds.ec2.compute.strategy.DescribeImagesParallel.apply(DescribeImagesParallel.java:
66)
at
org.jclouds.ec2.compute.suppliers.EC2ImageSupplier.get(EC2ImageSupplier.java:
94)
at
org.jclouds.ec2.compute.suppliers.EC2ImageSupplier.get(EC2ImageSupplier.java:
58)
at org.jclouds.compute.config.BaseComputeServiceContextModule
$9.get(BaseComputeServiceContextModule.java:251)
at org.jclouds.compute.config.BaseComputeServiceContextModule
$9.get(BaseComputeServiceContextModule.java:248)
at
org.jclouds.rest.suppliers.SetAndThrowAuthorizationExceptionSupplier.get(SetAndThrowAuthorizationExceptionSupplier.java:
49)
at
org.jclouds.concurrent.RetryOnTimeOutExceptionSupplier.get(RetryOnTimeOutExceptionSupplier.java:
47)
at
org.jclouds.util.Suppliers2$ExpiringMemoizingSupplier.get(Suppliers2.java:
130)
at
org.jclouds.rest.suppliers.MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.get(MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.java:
64)
at
org.jclouds.ec2.compute.internal.EC2TemplateBuilderImpl.getImages(EC2TemplateBuilderImpl.java:
116)
at
org.jclouds.compute.domain.internal.TemplateBuilderImpl.build(TemplateBuilderImpl.java:
614)
at bug.Eucalyptus.main(Eucalyptus.java:34)

[Adrian Cole]

Hi, Swetha.

Normally, you want to do a forum search before asking a question.

Here's a thread where this was tested:
http://groups.google.com/group/jclouds/browse_thread/thread/a4fa7c7201cff32f/d8c4d1568ebc9f78?lnk=gst&q=nova+eucalyptus#d8c4d1568ebc9f78


The endpoint url should look like: "http://mycloud:8773/services/Cloud"

I hope this helps.
-A

> --
> You received this message because you are subscribed to the Google Groups "jclouds" group.