• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Component/s: ec2-plugin
• Labels:

  None
• Environment:

  docker jenkins/jenkins:lts-slim
  ec2-plugin 1.42

[JENKINS-55556] EC2 unable to retrieve private IP (+ other buggy behaviour)

Günter Grodotzki created issue - 2019-01-13 13:27

Günter Grodotzki made changes - 2019-01-13 13:28

Issue Type

Original: New Feature [ 2 ]

New: Bug [ 1 ]

Günter Grodotzki made changes - 2019-01-13 13:28

Description

Original: 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.

New: 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...

Alistair Gilbert made changes - 2019-03-31 00:06

Comment

[ we made the changes to the iamrole and were able to spin the instace up fine. but now we are impacted by the second part of the issue where it spins up 10 instances in the backend. any suggestion for how to workaround that problem? ]

FABRIZIO MANFREDI made changes - 2019-06-26 15:30

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]