You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ins0mniac (JIRA)" <ji...@apache.org> on 2013/09/03 08:34:51 UTC
[jira] [Created] (JCLOUDS-261) key [aws-ec2] not in the list of
providers or apis: {}
ins0mniac created JCLOUDS-261:
---------------------------------
Summary: key [aws-ec2] not in the list of providers or apis: {}
Key: JCLOUDS-261
URL: https://issues.apache.org/jira/browse/JCLOUDS-261
Project: jclouds
Issue Type: Bug
Components: jclouds-compute
Affects Versions: 1.6.1
Environment: Jetspeed 2.2.3, Tomcat 7, Linux Mint 14/Mac 10.8.4
Reporter: ins0mniac
Priority: Critical
Lifecycle operations (start, stop etc) on a node seem to trigger this exception
java.util.NoSuchElementException: key [aws-ec2] not in the list of providers or apis: {}
at org.jclouds.ContextBuilder.newBuilder(ContextBuilder.java:170)
We are able to invoke provisioning methods (i.e. create/destroy nodes) on aws without any errors. However when we invoke the lifecycle methods, the first method always succeeds without errors. The second method always gets hit with the exception shown above.
The following jar files are available in WEB-INF/lib
aws-ec2-1.6.0-alpha.3.jar
ec2-1.6.0-alpha.3.jar
jclouds-blobstore-1.6.0-alpha.3.jar
jclouds-bouncycastle-1.6.0-alpha.3.jar
jclouds-compute-1.6.0-alpha.3.jar
jclouds-core-1.6.0-alpha.3.jar
jclouds-enterprise-1.6.0-alpha.3.jar
jclouds-joda-1.6.0-alpha.3.jar
jclouds-jsch-1.6.0-alpha.3.jar
jclouds-netty-1.6.0-alpha.3.jar
jclouds-slf4j-1.6.0-alpha.3.jar
jclouds-sshj-1.6.0-alpha.3.jar
s3-1.6.0-alpha.3.jar
Not sure what is causing this issue. It would be very helpful if someone could point us in the right direction to resolve this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira