-
Bug
-
Resolution: Not A Defect
-
Trivial
-
None
-
Jenkins 2.235.5, Amazon EC2 plugin 1.51
The master starts an EC2 spot instance and connects, but (apparently) breaks immediately after successfully establishing the connection. The log has the details:
Sep 03, 2020 1:41:03 PM hudson.plugins.ec2.EC2Cloud INFO: Node still not ready. Current status: Your Spot request is pending fulfillment. Sep 03, 2020 1:41:04 PM hudson.plugins.ec2.EC2Cloud INFO: Node still not ready. Current status: Your Spot request is pending fulfillment. Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: i-00827181fc21ac67b Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: Using private key elasticjenkins (SHA-1 fingerprint 29:f0:55:cd:37:ec:8c:30:4f:9e:6b:72:f3:94:fb:df) Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as admin Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: Connecting to null on port 22, with timeout 10000. Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: The SSH key ssh-ed25519 ff:de:e0:b4:0a:8b:fa:be:28:a3:9f:55:dd:a3:3c:3b has been automatically trusted for connections to EC2 (AWS EC2) - Verification Debian Linux 32 vcpus (sir-cfzg7xtm) Sep 03, 2020 1:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: Connected via SSH. Sep 03, 2020 1:41:06 PM hudson.plugins.ec2.EC2Cloud WARNING: Authentication failed. Trying again... Sep 03, 2020 1:41:36 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as admin Sep 03, 2020 1:41:36 PM hudson.plugins.ec2.EC2Cloud INFO: Connecting to null on port 22, with timeout 10000. Sep 03, 2020 1:41:36 PM hudson.plugins.ec2.EC2Cloud INFO: Connection allowed after the host key has been verified Sep 03, 2020 1:41:36 PM hudson.plugins.ec2.EC2Cloud INFO: Connected via SSH. Sep 03, 2020 1:41:36 PM hudson.plugins.ec2.EC2Cloud WARNING: Authentication failed. Trying again...
I have tried various combinations of "Connect by SSH Process", "Connection Strategy", and other cloud configuration parameters.
Is this a configuration problem or a bug in the EC2 plugin?
