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

Kubernetes plugin provisioning pods twice in 1.14.6

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • kubernetes-plugin
    • None

      Since 1.14.6 and it's update to kubernetes client 4.1.2, I started to observe weird behavior when plugin provisions two pods for one pod template. Second pod is exactly the same as first one but is spawned exactly 20 seconds after.

      I tried version 1.14.5 and it's working well (also tested 1.14.2, 1.14.0).

      Also it seems that SocketClosed exceptions caused by timeout on get operation became more frequent:
      Caused: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [Pod] with name: [terraform-deploy-fabric-cluster-cec-az-246-hc9xs-2z6rf] in namespace: [jenkins] failed.

        1. jenkins.log
          50 kB

          [JENKINS-56347] Kubernetes plugin provisioning pods twice in 1.14.6

          Filip Pytloun created issue -
          Filip Pytloun made changes -
          Description Original: Since 1.14.6 and it's update to kubernetes client 4.1.2, I started to observe weird behavior when plugin provisions two pods for one pod template. Second pod is exactly the same as first one but is spawned exactly 20 seconds after.

          I tried version 1.14.5 and it's working well (also tested 1.14.2, 1.14.0).

          Also it seems that SocketClosed exceptions caused by timeout on get operation became more frequent:
          Caused: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [Pod] with name: [terraform-deploy-fabric-cluster-cec-az-246-hc9xs-2z6rf] in namespace: [jenkins] failed.           		New: Since 1.14.6 and it's update to kubernetes client 4.1.2, I started to observe weird behavior when plugin provisions two pods for one pod template. Second pod is exactly the same as first one but is spawned exactly 20 seconds after.

          I tried version 1.14.5 and it's working well (also tested 1.14.2, 1.14.0).

          Also it seems that SocketClosed exceptions caused by timeout on get operation became more frequent:
           Caused: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [Pod] with name: [terraform-deploy-fabric-cluster-cec-az-246-hc9xs-2z6rf] in namespace: [jenkins] failed.
          Christian Tryti made changes -
          Attachment New: jenkins.log [ 46319 ]
          Carlos Sanchez made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Carlos Sanchez made changes -
          Remote Link New: This issue links to "PR-455 (Web Link)" [ 22703 ]
          Carlos Sanchez made changes -
          Link New: This issue is duplicated by JENKINS-56889 [ JENKINS-56889 ]
          Carlos Sanchez made changes -
          Link New: This issue is duplicated by JENKINS-56491 [ JENKINS-56491 ]
          Carlos Sanchez made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Carlos Sanchez made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]

            csanchez Carlos Sanchez
            genunix Filip Pytloun
            Votes:
            6 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: