Potential bug : CloudSigma blank drive

6 views
Skip to first unread message

Gérald Pereira

unread,
Jul 13, 2011, 11:13:57 AM7/13/11
to jclouds-dev
Hello,

I've encountered a situation that may be a bug.

To reproduce it, simply create a server with only a blank drive using
the CloudSigma console. No need to start the server.

Then execute the following main() :

public static void main(String[] args) {
JDKLoggingModule logging = new JDKLoggingModule();
ImmutableSet<Module> wiring = ImmutableSet.<Module> of(new
JschSshClientModule(), logging);
final ComputeServiceContext context = new
ComputeServiceContextFactory().createContext("cloudsigma-zrh", "xxxx",
"xxxxx", wiring);
ComputeService client = context.getComputeService();
client.listNodes();
context.close();
}

An IndexOutOfBoundException occurs :

13 juil. 2011 17:02:38 org.jclouds.logging.jdk.JDKLogger logWarn
ATTENTION: could not find a match in set for 1310568683707-3Drive
13 juil. 2011 17:02:38 org.jclouds.logging.jdk.JDKLogger logWarn
ATTENTION: could not find a match in set for 1310565610739-1Drive
Exception in thread "main" java.lang.IndexOutOfBoundsException:
index (0) must be less than size (0)
at
com.google.common.base.Preconditions.checkElementIndex(Preconditions.java:
301)
at
com.google.common.base.Preconditions.checkElementIndex(Preconditions.java:
280)
at com.google.common.collect.Iterables.get(Iterables.java:649)
at org.jclouds.cloudsigma.compute.functions.ServerInfoToNodeMetadata
$GetImageIdFromServer.apply(ServerInfoToNodeMetadata.java:154)
at org.jclouds.cloudsigma.compute.functions.ServerInfoToNodeMetadata
$GetImageIdFromServer.apply(ServerInfoToNodeMetadata.java:142)
at
org.jclouds.cloudsigma.compute.functions.ServerInfoToNodeMetadata.apply(ServerInfoToNodeMetadata.java:
96)
at
org.jclouds.cloudsigma.compute.functions.ServerInfoToNodeMetadata.apply(ServerInfoToNodeMetadata.java:
59)
at com.google.common.collect.Iterators$8.next(Iterators.java:765)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:
627)
at
com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:
141)
at
com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:
136)
at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:267)
at
org.jclouds.compute.internal.BaseComputeService.listNodes(BaseComputeService.java:
337)
at SigmaTest.main(SigmaTest.java:19)

Is this a bug or am I missing something ?

I tryed with both the beta 9b and the 1.0.0

Regards,

Gérald.

Adrian Cole

unread,
Jul 13, 2011, 11:43:01 AM7/13/11
to jclou...@googlegroups.com
Hi, Gérald.

This looks like a bug for sure. Do you mind attaching the FINE level
of jclouds.wire and jclouds.headers loggers when you do this? this
will show the server that is related to the error so we can that as a
test case, and put into an issue. If you can't no biggie, but
worthwhile asking :p

Cheers,
-A

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

Reply all
Reply to author
Forward
0 new messages