Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-69730

unable to launch agents via kubernetes jnlp.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • kubernetes-plugin
    • None
    • Ubuntu Bionic
      Jenkins LTS (2.361.1)
      OpenJDK 11.00.16
      Kubernetes 1.24.3

      I have a new jenkins instance in which I'm trying to launch kuberntes agents from Azure Kubernetes (v1.24.3).

      With the given Kuberntes agent config:

        - name: "default"
    containers:     
    - alwaysPullImage: true
      command: "jenkins-agent"
      args: ""
      image: "jenkins/inbound-agent:latest"
      livenessProbe:         
        failureThreshold: 0
        initialDelaySeconds: 0
        periodSeconds: 0
        successThreshold: 0
        timeoutSeconds: 0
      name: "jnlp"
      workingDir: "/home/jenkins/agent"
    id: "0f141aec-e7fb-4b13-8bf0-ecb0b25fb4ab"
    idleMinutes: 2
    imagePullSecrets:     
    - name: "regcred"
    label: "linux"
    namespace: "default"
    yamlMergeStrategy: "override"

      The node is created in Jenkins but never connects. In the Jenkins controller log, I see the following:

      Sep 28 14:58:30 jenkins001 jenkins[23731]: 2022-09-28 14:58:30.526+0000 [id=2068]#011INFO#011o.c.j.p.k.KubernetesLauncher#launch: Created Pod: kubernetes default/default-crzlb
Sep 28 14:58:30 jenkins001 jenkins[23731]: 2022-09-28 14:58:30.602+0000 [id=2056]#011INFO#011hudson.slaves.NodeProvisioner#update: default-crzlb provisioning successfully completed. We have 
now 5 computer(s)
Sep 28 14:58:32 jenkins001 jenkins[23731]: 2022-09-28 14:58:32.387+0000 [id=2068]#011INFO#011o.c.j.p.k.KubernetesLauncher#launch: Pod is running: kubernetes default/default-crzlb
Sep 28 14:59:02 jenkins001 jenkins[23731]: 2022-09-28 14:59:02.569+0000 [id=2068]#011INFO#011o.c.j.p.k.KubernetesLauncher#launch: Waiting for agent to connect (30/360): default-crzlb
Sep 28 14:59:02 jenkins001 jenkins[23731]: 2022-09-28 14:59:02.651+0000 [id=1975]#011INFO#011j.s.DefaultJnlpSlaveReceiver#channelClosed: Jetty (winstone)-1975 for default-crzlb terminated: j
ava.nio.channels.ClosedChannelException
Sep 28 14:59:02 jenkins001 jenkins[23731]: 2022-09-28 14:59:02.652+0000 [id=1975]#011INFO#011j.s.DefaultJnlpSlaveReceiver#channelClosed: Jetty (winstone)-1975 for default-crzlb terminated: j
ava.nio.channels.ClosedChannelException
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.458+0000 [id=754]#011INFO#011o.c.j.p.k.p.r.Reaper$TerminateAgentOnContainerTerminated#lambda$onEvent$1: default/default-crzlb C
ontainer jnlp was just terminated, so removing the corresponding Jenkins agent
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.467+0000 [id=754]#011INFO#011o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent default-crzlb
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.480+0000 [id=754]#011INFO#011o.c.j.p.k.KubernetesSlave#deleteSlavePod: Terminated Kubernetes instance for agent default/default
-crzlb
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.481+0000 [id=754]#011INFO#011o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer default-crzlb
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.570+0000 [id=2068]#011WARNING#011o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: defaul
t-crzlb, template=PodTemplate{id='0f141aec-e7fb-4b13-8bf0-ecb0b25fb4ab', name='default', namespace='default', slaveConnectTimeout=360, idleMinutes=1, label='linux default', containers=[Conta
inerTemplate{name='jnlp', image='inbound-agent:latest', alwaysPullImage=true, workingDir='/home/jenkins/agent', command='jenkins-agent', args='', resourceReques
tCpu='', resourceRequestMemory='', resourceRequestEphemeralStorage='', resourceLimitCpu='', resourceLimitMemory='', resourceLimitEphemeralStorage='', livenessProbe=ContainerLivenessProbe{exe
cArgs='', timeoutSeconds=0, initialDelaySeconds=0, failureThreshold=0, periodSeconds=0, successThreshold=0}}], imagePullSecrets=[PodImagePullSecret{name='regcred'}]}
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.570+0000 [id=2068]#011INFO#011o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent default-crzlb
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.574+0000 [id=2068]#011SEVERE#011o.c.j.p.k.KubernetesSlave#_terminate: Computer for agent is null: default-crzlb
Sep 28 14:59:03 jenkins001 jenkins[23731]: 2022-09-28 14:59:03.574+0000 [id=2068]#011INFO#011hudson.slaves.AbstractCloudSlave#terminate: FATAL: Computer for agent is null: default-crzlb

          [JENKINS-69730] unable to launch agents via kubernetes jnlp.

          Mike Delaney added a comment -

          As another data point, I am able to connect a macOS machine to Jenkins via JNLP:

           Sep 28, 2022 11:06:01 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using /tmp/jenkins/remoting as a remoting work directory
Sep 28, 2022 11:06:02 AM org.jenkinsci.remoting.engine.WorkDirManager setupLogging
INFO: Both error and output logs will be printed to /tmp/jenkins/remoting
Sep 28, 2022 11:06:04 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: darwin
Sep 28, 2022 11:06:04 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3044.vb_940a_a_e4f72e
Sep 28, 2022 11:06:04 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using /tmp/jenkins/remoting as a remoting work directory
Sep 28, 2022 11:06:04 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: WebSocket connection open
Sep 28, 2022 11:06:04 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected

          I did notice that the `jenkins/inbound-agent:latest` uses remoting `4.6` where as the darwin node is using `3044.vb_940a_a_e4f72e`. Maybe this is not a issue with the Kuberntes plugin but is an issue with the default container?

          Mike Delaney added a comment - As another data point, I am able to connect a macOS machine to Jenkins via JNLP: Sep 28, 2022 11:06:01 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /tmp/jenkins/remoting as a remoting work directory Sep 28, 2022 11:06:02 AM org.jenkinsci.remoting.engine.WorkDirManager setupLogging INFO: Both error and output logs will be printed to /tmp/jenkins/remoting Sep 28, 2022 11:06:04 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: darwin Sep 28, 2022 11:06:04 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3044.vb_940a_a_e4f72e Sep 28, 2022 11:06:04 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /tmp/jenkins/remoting as a remoting work directory Sep 28, 2022 11:06:04 AM hudson.remoting.jnlp.Main$CuiListener status INFO: WebSocket connection open Sep 28, 2022 11:06:04 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected I did notice that the `jenkins/inbound-agent:latest` uses remoting `4.6` where as the darwin node is using `3044.vb_940a_a_e4f72e`. Maybe this is not a issue with the Kuberntes plugin but is an issue with the default container?

          Mike Delaney added a comment -

          Turns out it was the version of remoting. Anything > 4.11 works from the Kubernetes plugin.

          Mike Delaney added a comment - Turns out it was the version of remoting. Anything > 4.11 works from the Kubernetes plugin.

            Unassigned Unassigned
            mdelaney Mike Delaney
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: