Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Cannot Reproduce
-
Jenkins ver 2.201
Yet Another Docker Plugin 0.1.4
SSH Slaves plugin 1.31.0
Description
After we updated the plugin to version 1.30.0 the docker plugin keeps provisioning because it is unable to find the credentials for the docker containers.
```
ERROR: Launching agent process aborted. java.lang.InterruptedException: Validate configuration: The selected credentials cannot be found at hudson.plugins.sshslaves.SSHLauncher.checkConfig(SSHLauncher.java:900) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:402) at hudson.slaves.DelegatingComputerLauncher.launch(DelegatingComputerLauncher.java:64) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
```
After downgrading back to version 1.28.1 everything seems to work again.
Changing the settings in the yet another docker plugin did not change anything.
Creating new credentials and selecting those didn't change anything either.
I also created an issue in github for this plugin because i do not know which one causes the problem (https://github.com/KostyaSha/yet-another-docker-plugin/issues/278)
I've created an environment with docker-compose using Jenkins Core 2.210, yep-another-docker-plugin 0.15 and ssh-slaves-plugin 1.31.0, all configured by JasC but yep-another-docker-plugin, it seems does not support JasC. I have configures key and user+password credentials both works as expected the agents are provisioned and execute the job. So testing the thing and debugging the code with the latest version of both plugins I could not find a reason to fail other than the credential does not exist, the check where seems to fail on your environment search for the ID of the credential that's it nothing less, nothing more.
this is my test environment https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-59879