[JIRA] (JENKINS-60623) Failed to count the # of live instances on Kubernetes after upgrade to 1.22.3 for slaves with multiple labes
Title: Message Title
Filip Brychta created an issue
Jenkins / JENKINS-60623
Failed to count the # of live instances on Kubernetes after upgrade to 1.22.3 for slaves with multiple labes
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
jenkins_err.log
Components:
kubernetes-plugin
Created:
2020-01-02 10:35
Environment:
Jenkins ver. 2.204.1 kubernetes-plugin 1.22.3 OpenShift Master: v3.11.104 Kubernetes Master: v1.11.0+d4cacc0
Priority:
Major
Reporter:
Filip Brychta
After upgrade to 1.22.3 from 1.21.3 no new slave pods were created and following exception was visible in the log: 2020-01-01 09:23:16.158+ [id=48] WARNING o.c.j.p.k.KubernetesCloud#provision: Failed to count the # of live instances on Kubernetes io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-slaves/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dkiali-build%20golang%20nodejs%20yarn. Message: found 'golang', expected: ',' or 'end of string'. Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=found 'golang', expected: ',' or 'end of string', metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}). Looks like the new plugin version is using spaces between labels in the API call but OpenShift API expects commas. Full exception is attached.
[JIRA] (JENKINS-56140) Failed to count the # of live instances on Kubernetes because of expired bearer token
Title: Message Title Filip Brychta commented on JENKINS-56140 Re: Failed to count the # of live instances on Kubernetes because of expired bearer token Thanks a lot for quick response. IIUC the PR#429 forces created clients to be flushed from the cache by default after 24 hours and newly created clients should get new token. This looks like a good solution to me. Thank you Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56140) Failed to count the # of live instances on Kubernetes because of expired bearer token
Title: Message Title
Filip Brychta created an issue
Jenkins / JENKINS-56140
Failed to count the # of live instances on Kubernetes because of expired bearer token
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-02-14 13:58
Environment:
Jenkins ver. 2.150.2 kubernetes-plugin 1.14.3 OpenShift Master: v3.9.30 Kubernetes Master: v1.9.1+a0ce1bc657
Priority:
Major
Reporter:
Filip Brychta
After upgrade to 1.14.3 from 1.12.7 everything was working fine but after 24 hours no new slave pods were created and following exception was visible in the log: Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log INFO: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401} Feb 11, 2019 3:53:01 PM okhttp3.internal.platform.Platform log INFO: <-- END HTTP (129-byte body) Feb 11, 2019 3:53:01 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision WARNING: Failed to count the # of live instances on Kubernetes io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://b22.jonqe.lab.eng.bos.redhat.com:8443/api/v1/namespaces/jenkins-slaves/pods?labelSelector=jenkins%3Dslave. Message: Unauthorized. Received status: Status(apiVersion=v1, code=401, details=null, kind=Status, message=Unauthorized, metadata=ListMeta(_continue=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Unauthorized, status=Failure, additionalProperties={}). at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:478) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:417) at
[JIRA] (JENKINS-52958) Slave pod is not removed when a job is finished
Title: Message Title Filip Brychta created an issue Jenkins / JENKINS-52958 Slave pod is not removed when a job is finished Issue Type: Bug Assignee: Carlos Sanchez Attachments: agent.log, master-okhttp3.log, master.log Components: kubernetes-plugin Created: 2018-08-09 10:23 Environment: Jenkins ver. 2.121.2 Kubernetes plugin 1.12.2 OpenShift Master: v3.9.30 Kubernetes Master: v1.9.1+a0ce1bc657 OpenShift Web Console: v3.9.30 Priority: Minor Reporter: Filip Brychta Slave pod is correctly created and agent is connected with jenkins master: Aug 09, 2018 8:49:49 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected When the job is done the plugin tries to terminate the slave: Aug 09, 2018 4:50:55 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate Terminating Kubernetes instance for agent jenkins-slave-centos-base-8ffg2 but it fails with: Aug 09, 2018 4:50:55 AM WARNING jenkins.slaves.DefaultJnlpSlaveReceiver channelClosed Computer.threadPoolForRemoting 760 for jenkins-slave-centos-base-8ffg2 terminated java.nio.channels.ClosedChannelException Agent tries to re-connect which fails: Aug 09, 2018 8:50:55 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated Aug 09, 2018 8:51:05 AM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1 onReconnect . INFO: [JNLP4-connect connection to jenkins2.bc.jonqe.lab.eng.bos.redhat.com/10.16.23.71:37355] Local headers refused by remote: Unknown client name: jenkins-slave-centos-base-8ffg2 Aug 09, 2018 8:51:08 AM
