[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera resolved JENKINS-22963 as Fixed Unable to connect to digitalocean cloud Fixed. See https://github.com/jenkinsci/jclouds-plugin/pull/69 Change By: Ignasi Barrera (03/Jun/14 9:15 PM) Status: Open Resolved Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud Yes, the plugin still does not have an option to specify the location where the node will be created, but that would be a nice addition. Mind opening a ticket to track it? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud I've just opened it: https://issues.jenkins-ci.org/browse/JENKINS-23168 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud This has already been fixed in jclouds, but you'll have to wait until its next bugfix release. If you can't wait, though, you'll be able to test it if you manually build the Jenkins plugin using the latest jclouds SNAPSHOT version. To do that: Clone the plugin repo: https://github.com/jenkinsci/jclouds-plugin Change the jclouds.version property to 1.7.3-SNAPSHOT. Add the jclouds snapshot repository to the pom.xml repositories section so the SNAPSHOT can be downloaded: repository idjclouds-snapshots/id urlhttps://repository.apache.org/content/repositories/snapshots/url snapshotsenabledtrue/enabled/snapshots /repository Build the plugin: mvn clean install hpi:run (have a lok at the README for further details. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera edited a comment on JENKINS-22963 Unable to connect to digitalocean cloud This has already been fixed in jclouds, but you'll have to wait until its next bugfix release. If you can't wait, though, you'll be able to test it if you manually build the Jenkins plugin using the latest jclouds SNAPSHOT version. To do that: Clone the plugin repo: https://github.com/jenkinsci/jclouds-plugin Change the jclouds.version property to 1.7.3-SNAPSHOT. Add the jclouds snapshot repository to the pom.xml repositories section so the SNAPSHOT can be downloaded: repository idjclouds-snapshots/id urlhttps://repository.apache.org/content/repositories/snapshots/url snapshotsenabledtrue/enabled/snapshots /repository Build the plugin: mvn clean install hpi:run (have a lok at the README for further details. After that you should be able to manually install the plugin in Jenkins from the plugin management page. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera stopped work on JENKINS-22963 Unable to connect to digitalocean cloud Change By: Ignasi Barrera (21/May/14 1:53 PM) Status: InProgress Open 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera edited a comment on JENKINS-22963 Unable to connect to digitalocean cloud This has already been fixed in jclouds, but you'll have to wait until its next bugfix release. If you can't wait, though, you'll be able to test it if you manually build the Jenkins plugin using the latest jclouds SNAPSHOT version. To do that: Clone the plugin repo: https://github.com/jenkinsci/jclouds-plugin Change the jclouds.version property to 1.7.3-SNAPSHOT. Add the jclouds snapshot repository to the pom.xml repositories section so the SNAPSHOT can be downloaded: repository idjclouds-snapshots/id urlhttps://repository.apache.org/content/repositories/snapshots/url snapshotsenabledtrue/enabled/snapshots /repository Build the plugin: mvn clean install (have a look at the README for further details. After that you should be able to manually install the plugin in Jenkins from the plugin management page. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud I've just compiled it as shown in my previous comment and uploaded it to my Jenkins instance to verify that the slugs can be used instead of the ids, and that old images are not causing trouble. Let's keep this open until jclouds 1.7.3 is released and we can upgrade the plugin to that version. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Fernando Witzke commented on JENKINS-22963 Unable to connect to digitalocean cloud Awesome, I'll try to build it locally to validate, it will be easier than taking snapshots of all my droplets. Thank you so much for such a quick workaround for that 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera started work on JENKINS-22963 Unable to connect to digitalocean cloud Change By: Ignasi Barrera (19/May/14 9:05 AM) Status: Open InProgress 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud Opened JCLOUDS-572 to address this by also adding support to use the slugs as the IDs. If you want to give it a try, the pull request is linked in the issue. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera assigned JENKINS-22963 to Ignasi Barrera Unable to connect to digitalocean cloud Change By: Ignasi Barrera (18/May/14 8:37 PM) Assignee: abayer IgnasiBarrera 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud This error is raised if the connection fails. To check the connection, the plugin will attempt to use the provided credentials to list the existing nodes. Are you providing the right client ID and api key? Make sure to leave the "endpoint URL" field blank. Jclouds will already set the appropriate one. Also check that the OpenStack zones field is blank. If the error persists, you can enable the jclouds wire logging as follows In the Jenkins Administration System logs, create a new logger. Add the "jclouds.wire", "jclouds.compute" and "jclouds.headers" loggers to it. Edit the jclouds plugin configuration that is having issues and add the following in the "Cloud Instance Tempaltes Advanced Custom JVM Options": -Djenkins.plugins.jclouds.compute.ComputeLogger.wireLogging=true 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Fernando Witzke updated JENKINS-22963 Unable to connect to digitalocean cloud Change By: Fernando Witzke (18/May/14 11:08 PM) Attachment: jclouds.logs 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Fernando Witzke commented on JENKINS-22963 Unable to connect to digitalocean cloud I double checked and I'm providing the right client id and api key. In fact I tried putting the wrong api key just to test, and when I do that I do get an "Access Denied" error. I've enabled the logging as suggested, it looks like it successfully got the information from digital ocean, but the error itself is not logged. This is where the exception is handled, but I don't think it's logged anywhere. I'm attaching the logs I got, just hiding my api key. Thanks for the help. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Fernando Witzke commented on JENKINS-22963 Unable to connect to digitalocean cloud Another thing, I tried launching a slave manually and got the following exception at DropletToNodeMetadata#94: Caused by: java.lang.NullPointerException at org.jclouds.digitalocean.compute.functions.DropletToNodeMetadata.apply(DropletToNodeMetadata.java:94) at org.jclouds.digitalocean.compute.functions.DropletToNodeMetadata.apply(DropletToNodeMetadata.java:51) at shaded.com.google.common.base.Functions$FunctionComposition.apply(Functions.java:210) at shaded.com.google.common.collect.Iterators$8.transform(Iterators.java:794) at shaded.com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48) at shaded.com.google.common.collect.Iterators$7.computeNext(Iterators.java:646) at shaded.com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at shaded.com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at shaded.com.google.common.collect.Iterators.addAll(Iterators.java:356) at shaded.com.google.common.collect.Iterables.addAll(Iterables.java:351) at shaded.com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328) at org.jclouds.compute.internal.BaseComputeService.listNodes(BaseComputeService.java:340) at jenkins.plugins.jclouds.compute.JCloudsCloud.getRunningNodesCount(JCloudsCloud.java:295) at jenkins.plugins.jclouds.compute.JCloudsCloud.doProvision(JCloudsCloud.java:278) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) ... 63 more 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Fernando Witzke commented on JENKINS-22963 Unable to connect to digitalocean cloud I think I found the issue: while listing the existing droplets, it tries to retrieve the droplet image details from the 'images list' provided by digital ocean api. The problem is that these ids change. In my case, my droplets have an associated image id which is not in the 'current images list' anymore, and so it can't find the image details this way, and the NPE happens. somehow related: they've added support for slugs instead of ids 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud There is an ongoing patch for that here: https://github.com/jclouds/jclouds-labs/pull/58 But seeing your comment (many thanks for the investigation!) I think the right fix is to use the slugs instead of the ids everywhere. The change should be easy: we just need to change the classes in the compute.functions package to set the slug in the id field and change the DigitalOceanComputeServiceAdapter accordingly. I'll try to have a patch ASAP for this (if you don't beat me with a PR https://wiki.apache.org/jclouds/How%20to%20Contribute). 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera commented on JENKINS-22963 Unable to connect to digitalocean cloud BTW, the plugin will fail as long as the droplet that uses the old image exists. To workaround this, you can take a snapshot of that droplet, destroy it, and create it again from the snapshot. The snapshot will have a new image id and the plugin shouldn't find old ids. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
