-
Bug
-
Resolution: Duplicate
-
Major
-
Kubernetes plugin 1.30.2
Jenkins 2.303.2 LTS
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
However, kubernetes-plugin release 1.30.2 changed the default agent container image to jdk11 when controller is also running on jdk11.
This doesn't play nice without fixing jnlp agent to use jdk8 container image.
- duplicates
-
JENKINS-61212 CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
-
- Closed
-
[JENKINS-66836] Handshake response not received with release 1.30.2 and We
Description |
Original:
When Jenkins is launching a new slave/agent pod, it never times out and keep trying to launch a new pod when the current is failing.
For example, we had an issue of miss configuration made the agent pod to be created in a namespaces where there're no pull credentials. In this case we had a cron job which got stuck and kept trying to created a pod *for 2 days* (until manually aborted), although the issue has been already resolved. It didn't get the code update since the job has to be stopped and rebuilt. I went through the whole relevant documentation to find proper timeout setting, but nothing worked. I thought *slaveConnectTimeout* should do the job, but it didn't help, as well as setting org.csanchez.jenkins.plugins.kubernetes.PodTemplate.connectionTimeout system property. What I'm looking for is an option to set a timeout that kills the jobs if it can't launch an agent pod after x seconds. |
Environment |
Original:
Kubernetes plugin 1.30.1
Jenkins 2.263.4 LTS |
New:
Kubernetes plugin 1.30.2
Jenkins 2.303.2 LTS |
Summary | Original: Handshake response not received with release 1.30.2 | New: Handshake response not received with release 1.30.2 with WebSockets |
Summary | Original: Handshake response not received with release 1.30.2 with WebSockets | New: Handshake response not received with release 1.30.2 and WebSockets |
Description |
New:
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
|
Description |
Original:
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
|
New:
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
However, [kubernetes-plugin|https://issues.jenkins.io/issues/?jql=project+%3D+JENKINS+AND+component+%3D+kubernetes-plugin] release 1.30.2 changed the default agent container image to `jdk11` |
Description |
Original:
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
However, [kubernetes-plugin|https://issues.jenkins.io/issues/?jql=project+%3D+JENKINS+AND+component+%3D+kubernetes-plugin] release 1.30.2 changed the default agent container image to `jdk11` |
New:
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
However, [kubernetes-plugin|https://issues.jenkins.io/issues/?jql=project+%3D+JENKINS+AND+component+%3D+kubernetes-plugin] release 1.30.2 changed the default agent container image to jdk11. This doesn't play nice witout fixing jnlp agent to use jdk8 container image. |
Description |
Original:
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
However, [kubernetes-plugin|https://issues.jenkins.io/issues/?jql=project+%3D+JENKINS+AND+component+%3D+kubernetes-plugin] release 1.30.2 changed the default agent container image to jdk11. This doesn't play nice witout fixing jnlp agent to use jdk8 container image. |
New:
https://issues.jenkins.io/browse/JENKINS-61212 seems like an issue that have no time line to be fixed.
However, [kubernetes-plugin|https://issues.jenkins.io/issues/?jql=project+%3D+JENKINS+AND+component+%3D+kubernetes-plugin] release 1.30.2 changed the default agent container image to jdk11 when controller is also running on jdk11. This doesn't play nice witout fixing jnlp agent to use jdk8 container image. |
Summary | Original: Handshake response not received with release 1.30.2 and WebSockets | New: Handshake response not received with release 1.30.2 and We |
Labels | New: java11-compatibility jnlp websocket |