Still waiting to schedule task Waiting for next available executor

Using Jenkins
1

Hi,
I am trying to deploy windows images as kubernetes pods in K8S cluster through jenkins by using Jenkinsfile.
So this is my Jenkinsfile
pipeline {
agent {
kubernetes {
cloud ‘windows-cluster’
label ‘windows-agent’
yaml “”"
apiVersion: v1
kind: Pod
metadata:
labels:
app: windows-agent
spec:
containers:
- name: jnlp
image: jenkins/inbound-agent:windowsservercore-ltsc2019
- name: dotnet
image: mcr.microsoft.com/dotnet/sdk:6.0
command: [‘cmd’]
args: [‘k’]
tty: true
nodeSelector:
kubernetes.io/os: windows

        """
        
}
}
stages {
    stage('Build') {
         steps {
            container('dotnet') {
                bat 'dotnet --version'
                
               
           }
         }
    }
    // stage('Run .net commands') {
    //     steps {
    //         container('dotnet-pod') {
    //             bat 'dotnet build'
    //         }
            
    //     }
    // }

}
}
whatever I have mentioned in Jenkinsfile I have configured in backed cloud configuration(kubernetes cloud).
so when I try to run this Job. In log file it is showing
still waiting to schedule task waiting for next available executor for 1 to 2 hours so finally aborted that job.
this is the issue i am facing. If anyone know the solution please reply to this question.
Thanks

2

Hi, I don’t know kubernetes. But I had faced a similar executor issue when using nodes. You can change the no. of executors . Refer the Screen shot below

image
image1147×280 15.4 KB

3

Thank You @cuckuduku for the reply
So I have increased Number of executors to 5 so we are still facing this error
Still waiting to schedule task
‘Jenkins’ doesn’t have label ‘linux-app_20-xww1j’
even though we have mentioned label in the backend cloud configuration.

4

label ‘linux-app_20-xww1j’ is not there in Jenkins. You can attach the screenshot of nodes or labels, so that I can see

5

@ganesh1143 Is this issue resolved for you. Actually I am also facing similar issue.
Where my dynamic kaniko agent gets created in k8s.

Please let me know if you are able to resolve this.
Thanks in advance.