-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Kubernetes
After upgrading to kubernetes-plugin:0.6 from 0.5 we've started getting the exception below when trying to run a build after the jenkins pod is first started.
As a temporary workaround if I go into http://jenkins/configure and click `Save` without changing any config, Nodes are then able to be scheduled.
Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 May 15, 2016 9:32:33 PM SEVERE org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud Error in provisioning; slave=KubernetesSlave name: , template=org.csanchez.jenkins.plugins.kubernetes.PodTemplate@20128103 May 15, 2016 9:32:43 PM WARNING hudson.slaves.NodeProvisioner Provisioned agent Kubernetes Pod Template failed to launch java.lang.NullPointerException at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getNodeSelectorMap(KubernetesCloud.java:278) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getPodTemplate(KubernetesCloud.java:267) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.access$100(KubernetesCloud.java:60) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:358) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:340) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) 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)
