[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov commented on JENKINS-58143 Re: Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized The solution provided by Carlos Sanchez helped. The ticket can be closed. Carlos Sanchez 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.7900.1561455420307%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov commented on JENKINS-58143 Re: Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized I added the option + restarted pod. Monitoring how it behaves. Carlos Sanchez 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.7541.1561393560285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov updated an issue Jenkins / JENKINS-58143 Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized Change By: Andrei Stepanov Attachment: jenkins-log-58143.txt 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.5506.1561130520208%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov updated an issue Jenkins / JENKINS-58143 Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized Change By: Andrei Stepanov Priority: Minor Major 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.5502.1561129440379%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Andrei Stepanov created an issue Jenkins / JENKINS-58143 Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-06-21 15:03 Priority: 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
[JIRA] (JENKINS-54247) Add to TROUBLESHOOTING how to backup/restore current keys
Title: Message Title Andrei Stepanov commented on JENKINS-54247 Re: Add to TROUBLESHOOTING how to backup/restore current keys Okay, thank you. I think this ticket can be closed. 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-54247) Add to TROUBLESHOOTING how to backup/restore current keys
Title: Message Title Andrei Stepanov commented on JENKINS-54247 Re: Add to TROUBLESHOOTING how to backup/restore current keys Hi, thank you for answer. I our Jenkins: checkbox "Encryption Configuration" is not set. Does this mean that Jenkins master doesn't have personal private key to talk to idP? Could you please just in steps say what I need to back up, and how to restore? We do not use "Encryption Configuration" checkbox is SAML plugin configuration. 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-54247) Add to TROUBLESHOOTING how to backup/restore current keys
Title: Message Title Andrei Stepanov created an issue Jenkins / JENKINS-54247 Add to TROUBLESHOOTING how to backup/restore current keys Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2018-10-25 10:37 Labels: plugin SAML2 SAML rfe Priority: Minor Reporter: Andrei Stepanov Hi, I tried to find a way to save current keys used for saml auth. But it was unsuccessful. I can backup metadata (directly from the plugin configuration link). Is there way to backup current keys that uses SAML plugin? For example, we redeployed completely from scratch Jenkins master, is there a way to use the same metadata without reconfiguring idP? It would be nice to add this info to : https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md Thank you! Add Comment
