-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
Dockerized Jenkins (2.80-2.91) Running on a Azure Kubernetes
Kubernetes Plugin (1.1)
Operating System CoreOS
Java 1.8
Web Browser - Several Chrome 55, Safari 11.0.1
The configuration of Kuberenetes starts with
Connection Timeout 5
Read Timeout 15
After several runs of jobs (happens after a day and sometimes a month) the configuration is reseted to
Connection Timeout 0
Read Timeout 0
Any change via browser to change it with Apply/Save doesn't pass and the values are kept to 0
This result is creating slaves that starts with error, probably due to lack of contact with master.
Workaround
----------------
kubectl exec -it jenkins_pod bash
edit the /var/jenkins_home/config.xml
edit the variables.
Delete all slaves, afterward kill the master pod. The running pod starts with 5 and 15. and activity is back to normal
I put it on Major but it should be Critical, only because I have a workaround for this.
[JENKINS-48189] Kubernetes Plugin - Reset Connection and Read Timeout to 0 and fails to change back
Epic Link | New: JENKINS-36178 [ 172150 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Epic Link | Original: JENKINS-36178 [ 172150 ] |
Rank | New: Ranked higher |
Rank | New: Ranked higher |
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |