jx: Jenkins X stuck waiting for next available executor

Summary

Jenkins X stuck waiting for next available executor.

Steps to reproduce the behavior

Installed jenkins x using jx install --provider=aws Imported project using jx import --no-draft from git

Tried to execute the project

Expected behavior

Jenkins X stuck waiting for next available executor

Actual behavior

Jenkins X should create a pod and execute the job.

Jx version

The output of jx version is:

NAME               VERSION
jx                 2.0.147
jenkins x platform 2.0.330
Kubernetes cluster v1.11.8
kubectl            v1.14.2
helm client        Client: v2.13.1+g618447c
git                git version 2.20.1 (Apple Git-117)
Operating System   Mac OS X 10.14.4 build 18E226

Jenkins type

  • Next Generation (Tekton + Prow)
  • Classic Jenkins
  • Serverless Jenkins (JenkinsFileRunner + Prow)

Kubernetes cluster

Custom k8s cluster on AWS

Operating system / Environment

MacOS

Also how does one install things like maven,pip in case of JenkinsX since I am using the --no-draft options?

I tried restarting jenkins-x by killing the pod.

I see the following lines : INFO: Jenkins is fully up and running May 22, 2019 9:21:54 AM com.cloudbees.jenkins.support.SupportPlugin writeBundle WARNING: Could not attach ''nodes/master/pipeline-timings.txt'' to support bundle java.io.IOException: test/webAutomation/master #1 did not yet start at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:928) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$PipelineTimings$1.writeTo(CpsFlowExecution.java:1902) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:309) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:276) at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl.lambda$doRun$0(SupportPlugin.java:764) at java.lang.Thread.run(Thread.java:748)

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 15 (4 by maintainers)

Most upvoted comments

@doc-olliday For what it’s worth, after updating all of the plugins (except the one that said it would require any configured jobs / pipelines to be rebuilt), this is resolved for me.

Happened with an on-prem cluster today. Updating plugins resolved the issue.