-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.303.2
Kubernetes plugin 1.30.5
When a pod gets launched and something goes wrong, the exception is hidden as an ArrayIndexOutOfBoundsException is thrown within the catch clause.
Introduced with https://github.com/jenkinsci/kubernetes-plugin/pull/1050/files
java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0 at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:256) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:293) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) ...
As it directly tries to access the array without a check if the array even contains any suppressed Throwables: https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesLauncher.java#L256
Looks like this has already been fixed in 1.30.6 via this commit...
https://github.com/jenkinsci/kubernetes-plugin/commit/1f33777e941cbde91a18604a8e996bd59d853f4c