-
Bug
-
Resolution: Unresolved
-
Major
I've just upgraded our EC2 plugin to the latest (1.50.2) and have found our nodes are not spinning up.
They perpetually loop with the following logs:
May 08, 2020 4:12:23 PM hudson.plugins.ec2.EC2Cloud INFO: The line with the key doesn't have the required format. Found: "ssh-ed25519 AAAAC3Nzarestofkeygoeshere ". Expected a line with this text: "ALGORITHM THEHOSTKEY", example: "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR "
Based on this:
String[] parts = line.split(" ");
if (parts.length > 2) {
The example will never work:
{{ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR }}
will never split into > 2 pieces as the code says. E.g.: https://repl.it/repls/FoolishCrookedWebsite
Either I'm misunderstanding how this is meant to work, or the error message is unclear.
I've not done anything to change our configuration other than upgrading the plugin.
[JENKINS-62221] EC2 plugin perpetually loops unable to verify key for host
I had the same issue. I set the Host Key Verification Strategy to off, and the nodes connected successfully.
That gives a warning on the management page about MITM attacks, but its a workaround until it can be fixed.
Aaron Mell
added a comment - - edited I had the same issue. I set the Host Key Verification Strategy to off, and the nodes connected successfully.
That gives a warning on the management page about MITM attacks, but its a workaround until it can be fixed. 
HI,
I have exactly the same problem following an update to the latest plugin.
From the configuration page, the connection test works which makes it believe that everything works just fine whereas the plugin is unable to connect to the agents. Any ETA to when this will be resolved?