[JIRA] (JENKINS-16088) JClouds Plugin creates too many instances and fails to launch Jenkins slaves

2016-11-05 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fritz Elfert closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Out of date  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-16088  
 
 
  JClouds Plugin creates too many instances and fails to launch Jenkins slaves   
 

  
 
 
 
 

 
Change By: 
 Fritz Elfert  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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 

[JIRA] (JENKINS-16088) JClouds Plugin creates too many instances and fails to launch Jenkins slaves

2012-12-10 Thread jesusau...@inbox.com (JIRA)














































Jonathan Harker
 created  JENKINS-16088


JClouds Plugin creates too many instances and fails to launch Jenkins slaves















Issue Type:


Bug



Assignee:


abayer



Components:


jclouds



Created:


10/Dec/12 10:42 PM



Description:


A simple job which creates a single jclouds instance then runs `echo` on that instance fails  creating several nova instances on the account, none of which are listed in jenkins as nodes.

The instance template uses a base ubuntu precise image, with Allow Sudo on and the following init script defined:


#!/bin/bash

apt-add-repository -y ppa:saltstack/salt
apt-get -y update
apt-get install -y build-essential
apt-get install -y git
apt-get install -y python-dev
apt-get install -y python-novaclient
apt-get install -y python-jinja2
apt-get install -y salt-master


The console output is:


Started by user anonymous
EnvInject - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/jobs/create-salt-slave-az1/workspace
Queuing cloud instance: #0 1, HPCS salt-az1
ERROR: Exception creating a node: org.jclouds.compute.RunNodesException: error running 1 node group(salt-az1) location(az-1.region-a.geo-1) image(8419) size(101) options({scriptPresent=true, userMetadata={Name=salt-az1}, generateKeyPair=true})
Execution failures:

1) ExecutionException on salt-az1-348:
java.util.concurrent.ExecutionException: java.util.NoSuchElementException
	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.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
Caused by: java.util.NoSuchElementException
	at com.google.common.collect.Iterables.getLast(Iterables.java:797)
	at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:100)
	at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:55)
	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


1 errors
Node failures:

0 errors
ERROR: Exception creating a node: org.jclouds.compute.RunNodesException: error running 1 node group(salt-az1) location(az-1.region-a.geo-1) image(8419) size(101) options({scriptPresent=true, userMetadata={Name=salt-az1}, generateKeyPair=true})
Execution failures:

1) ExecutionException on salt-az1-768:
java.util.concurrent.ExecutionException: java.util.NoSuchElementException
	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.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
Caused by: java.util.NoSuchElementException
	at com.google.common.collect.Iterables.getLast(Iterables.java:797)
	at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:100)
	at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:55)
	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


1 errors
Node failures:

0 errors
ERROR: Exception creating a node: 

[JIRA] (JENKINS-16088) JClouds Plugin creates too many instances and fails to launch Jenkins slaves

2012-12-10 Thread aba...@java.net (JIRA)














































abayer
 commented on  JENKINS-16088


JClouds Plugin creates too many instances and fails to launch Jenkins slaves















Looks like jclouds isn't able to allocate an IP to your instances?



























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