-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: ec2-plugin
-
Labels:None
-
Environment:docker jenkins/jenkins:lts-slim
ec2-plugin 1.42
-
Similar Issues:
I must say any version > 1.39 seems ultra buggy for our use case (ec2 spot instances @ c4.xlarge):
- when launching manually the plugin can not pick up the private IP and tries to connect to "null:22" endlessly
- when launched "on-demand" the plugin will launch 10+ spot instances, non of them will work though
Downgrading to 1.39 makes the plugin work on the exact same setup. Curious why AWS is not stepping in to give this plugin some love...
On Jenkins 2.150.2 EC2 plugin 1.42 we get this behavior intermittently. We oscillate between this error and the error in JENKINS-55639.
With the null:22 error we additionally get the horrible side effect that the script continues to connect to the master node and runs the init script. Just by chance the init script I had in place wasn't destructive to the master. Now I have a little addition to my init script at the top:
master=jenkins-master host=$(hostname -s) if [ $host == $master ] then echo "This is the master node! Exiting!!!" exit 1 else echo "Server is a spot node, apparently. Better yet, it's NOT the master node. Continuing..." fi
In the 1.43 will be added an option to specify how to connect to slave (private or public)
Is there an estimate of when 1.43 will be released?
1.43 has been released
We are using spot instances too. Configuring master to connect to slaves using neither public IP or private IP works. Always
Jan 21, 2019 6:41:58 AM hudson.plugins.ec2.EC2Cloud
INFO: Failed to connect via ssh: There was a problem while connecting to null:22
The plugin is indeed unusable for spot instance use case since 1.40, there was always different error in each version.