-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins version 2.461 running in docker, built from the image jenkins/jenkins:jdk:17. Agent is built from the image jenkins/ssh-agent:jdk17
Manually creating a node via <jenkinsurl>/manage/computer/createItem fails, redirecting to a vague 'error processing request' page.
Error only occurs when the launch method "Docker variant of launch agents via SSH with SSH key injection" is set in the form for creating a new node.
I can provide more information, I'm not sure what would be helpful beyond what I've already supplied, please advise if more info is needed.
Stack trace below:
2024-06-08 22:50:52 org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class io.jenkins.docker.connector.DockerComputerSSHConnector$InjectKeySSHLauncher
2024-06-08 22:50:52 at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:291)
2024-06-08 22:50:52 at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:940)
2024-06-08 22:50:52 at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:830)
2024-06-08 22:50:52 Caused: java.lang.IllegalArgumentException: Failed to instantiate class io.jenkins.docker.connector.DockerComputerSSHConnector$InjectKeySSHLauncher from {"stapler-class":"io.jenkins.docker.connector.DockerComputerSSHConnector$InjectKeySSHLauncher","$class":"io.jenkins.docker.connector.DockerComputerSSHConnector$InjectKeySSHLauncher","host":"0.0.0.0","includeUser":"false","credentialsId":"44c80487-025d-48a1-b538-dc23eaaf5bc8","":"2","sshHostKeyVerificationStrategy":
,"port":"22","javaPath":"","jvmOptions":"","prefixStartSlaveCmd":"","suffixStartSlaveCmd":"","launchTimeoutSeconds":"","maxNumRetries":"","retryWaitTime":"","tcpNoDelay":true,"workDir":"","oldCommand":""}
2024-06-08 22:50:52 at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:834)
2024-06-08 22:50:52 at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:589)
2024-06-08 22:50:52 at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:584)
2024-06-08 22:50:52 at hudson.model.Descriptor.bindJSON(Descriptor.java:625)
2024-06-08 22:50:52 at hudson.model.Descriptor.newInstance(Descriptor.java:595)
2024-06-08 22:50:52 Caused: java.lang.LinkageError: Failed to instantiate class io.jenkins.docker.connector.DockerComputerSSHConnector$InjectKeySSHLauncher from {"stapler-class":"io.jenkins.docker.connector.DockerComputerSSHConnector$InjectKeySSHLauncher","$class":"io.jenkins.docker.connector.DockerComputerSSHConnector$InjectKeySSHLauncher","host":"0.0.0.0","includeUser":"false","credentialsId":"44c80487-025d-48a1-b538-dc23eaaf5bc8","":"2","sshHostKeyVerificationStrategy":
,"port":"22","javaPath":"","jvmOptions":"","prefixStartSlaveCmd":"","suffixStartSlaveCmd":"","launchTimeoutSeconds":"","maxNumRetries":"","retryWaitTime":"","tcpNoDelay":true,"workDir":"","oldCommand":""}
The last commit to the docker slaves plugin was 4 years ago. The last commit by a maintainer was over 6 years ago.
Its plugin health score is 79%. While it is not listed as "up for adoption" I think that it is safe to assume the plugin is no longer being maintained. You could adopt the plugin or you could switch to use a different method to launch your agents.