Unable to connect to agents after upgrading to newest plugin version

[Yethal]

Testing done

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[rammanokar-plateron]

I am also facing this issue with Amazon EC2 plugin 1822.v87175d209b_b_5, Issue has been resolved after downgrading the plugin,

logs:

java.io.EOFException: unexpected stream termination
	at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:478)
	at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:422)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:440)
	at PluginClassLoader for ec2//hudson.plugins.ec2.ssh.EC2UnixLauncher.launchRemotingAgent(EC2UnixLauncher.java:453)
	at PluginClassLoader for ec2//hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:402)
	at PluginClassLoader for ec2//hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:55)
	at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:297)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:80)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
	```
--

[escoem]

#1022 (comment)

[lemeurherveCB]

I can't file this as an issue because repo has issues disabled

@Yethal indeed GitHub issues are disabled on most of jenkinsci org repositories.

Here is the issue tracker to use for Jenkins Core and its plugins: https://issues.jenkins.io

Existing issues concerning ec2-plugin: https://issues.jenkins.io/browse/JENKINS-75187?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20ec2-plugin

[lemeurherveCB]

@Yethal Could you open a corresponding issue on https://issues.jenkins.io and close this PR please?

[lemeurherveCB]

@Yethal Could you open a corresponding issue on https://issues.jenkins.io and close this PR please?

There is already an issue for this error opened 4 hours ago: https://issues.jenkins.io/browse/JENKINS-75187

This PR should be closed.

[Yethal]

@lemeurherveCB Maybe instead of closing it the corresponding change should be reverted so that people who do periodic plugin updates don't end up with broken instances?

[lemeurherveCB]

@lemeurherveCB Maybe instead of closing it the corresponding change should be reverted so that people who do periodic plugin updates don't end up with broken instances?

This discussion should happen in the https://issues.jenkins.io/browse/JENKINS-75187 issue, not here.

[fcojfernandez]

fix should be ready in https://github.com/jenkinsci/ec2-plugin/releases/tag/1823.v828850f7f155