[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized

18 views
Skip to first unread message

astepano@redhat.com (JIRA)

unread,
Jun 21, 2019, 11:04:03 AM6/21/19
to jenkinsc...@googlegroups.com
Andrei Stepanov created an issue
 
Jenkins / Improvement JENKINS-58143
Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Issue Type: Improvement Improvement
Assignee: Carlos Sanchez
Components: kubernetes-plugin
Created: 2019-06-21 15:03
Priority: Minor Minor
Reporter: Andrei Stepanov

Hello,

 

Jun 21, 2019 2:10:17 PM FINE io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager scheduleReconnectSubmitting reconnect task to the executor
Jun 21, 2019 2:10:17 PM WARNING io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$2 onFailureExec Failure: HTTP 401, Status: 401 - Unauthorized
java.net.ProtocolException: Expected HTTP 101 response but was '401 Unauthorized'
	at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:219)
	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:186)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Jun 21, 2019 2:10:17 PM FINE io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$3 executeScheduling reconnect task

 

 

It happens on from time to time. We have other Jenkins master in the same project. The other master works good. 

Kubernetes plugins in: 1.16.1

Jenkins master is: Jenkins ver. 2.164.2

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

astepano@redhat.com (JIRA)

unread,
Jun 21, 2019, 11:04:03 AM6/21/19
to jenkinsc...@googlegroups.com

astepano@redhat.com (JIRA)

unread,
Jun 21, 2019, 11:22:02 AM6/21/19
to jenkinsc...@googlegroups.com

jenkins-ci@carlossanchez.eu (JIRA)

unread,
Jun 21, 2019, 11:26:02 AM6/21/19
to jenkinsc...@googlegroups.com
Carlos Sanchez commented on Improvement JENKINS-58143
 
Re: Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized

have you tried running with a lower number of seconds in -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=86400
https://github.com/jenkinsci/kubernetes-plugin/pull/429

astepano@redhat.com (JIRA)

unread,
Jun 24, 2019, 12:26:02 PM6/24/19
to jenkinsc...@googlegroups.com

I added the option + restarted pod. Monitoring how it behaves. Carlos Sanchez thank you!

astepano@redhat.com (JIRA)

unread,
Jun 25, 2019, 5:37:03 AM6/25/19
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Jul 8, 2019, 2:42:02 PM7/8/19
to jenkinsc...@googlegroups.com

Good that there was a workaround, but you should not need to set an obscure system property just to make the system work. Any known way to reproduce from scratch?

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:24:01 PM7/16/19
to jenkinsc...@googlegroups.com

I am guessing you are using some sort of time-limited authentication to the cluster. What specifically do your credentials look like? The current “fix” merely refreshes the client after a day, which is better than nothing, but not very discoverable. Possible resolutions include

  • Printing a meaningful error about an expired token somewhere that an administrator will see it (not just the system log).
  • Automatically asking to refresh the token by some means.

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:43:25 PM7/16/19
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Jul 18, 2019, 10:35:01 AM7/18/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages