[JIRA] (JENKINS-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Carlos Sanchez resolved as Cannot Reproduce This seems to work after increasing the liveness checks making the master not restart twice Jenkins / JENKINS-49956 Kubernetes agent fails to reconnect on master restarts Change By: Carlos Sanchez Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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...@googl
[JIRA] (JENKINS-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Oleg Nenashev commented on JENKINS-49956 Re: Kubernetes agent fails to reconnect on master restarts From Remoting perspective it is a default behavior for fatal errors. What is "fatal" is separate topic, e.g. see JENKINS-46515. Generally the advanced failover behavior should be implemented by users of slave.jar, e.g. see https://github.com/jenkinsci/windows-slave-installer-module/blob/master/src/main/resources/org/jenkinsci/modules/windows_slave_installer/jenkins-slave.xml#L52 . Feel free to submit feature requests to Remoting though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Carlos Sanchez commented on JENKINS-49956 Re: Kubernetes agent fails to reconnect on master restarts My guess is that it has to do with the double restart because there are tests that exercise durable pipeline at https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/test/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/RestartPipelineTest.java In my instance I increased the time for health checks to avoid the double restart Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Carlos Sanchez commented on JENKINS-49956 Re: Kubernetes agent fails to reconnect on master restarts 1. yes, the docker agent dies after the last log Failed to send back a reply to the request 2. No, it's the standard https://github.com/jenkinsci/docker-jnlp-slave image Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Oleg Nenashev commented on JENKINS-49956 Re: Kubernetes agent fails to reconnect on master restarts Carlos Sanchez 1. does the Remoting process die after the error in the log? I'd guess so, it should be a fatal error 2. Do the docker images you use have any failover configured outside the remoting executable? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49956 Kubernetes agent fails to reconnect on master restarts Change By: Oleg Nenashev Labels: remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-49956 Kubernetes agent fails to reconnect on master restarts Change By: Carlos Sanchez After restarting the master for plugin upgrades the agent fails to reconnectmaster logs {code}Mar 06, 2018 4:50:23 PM jenkins.model.Jenkins$24 runSEVERE: Restarting VM as requested by xxxMar 06, 2018 4:50:23 PM jenkins.model.Jenkins cleanUpINFO: Stopping JenkinsMar 06, 2018 4:50:23 PM jenkins.model.Jenkins$19 onAttainedINFO: Started terminationMar 06, 2018 4:50:23 PM jenkins.model.Jenkins$19 onAttainedINFO: Completed terminationMar 06, 2018 4:50:23 PM jenkins.model.Jenkins _cleanUpDisconnectComputersINFO: Starting node disconnectionMar 06, 2018 4:50:23 PM jenkins.slaves.DefaultJnlpSlaveReceiver channelClosedWARNING: safe-restart thread for artifact-manager-s3-c7701-0rmp3 terminatedjava.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.remoting.Channel.close(Channel.java:1358) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:737) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:704) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:88) at jenkins.model.Jenkins.access$2000(Jenkins.java:304) at jenkins.model.Jenkins$20.run(Jenkins.java:3367) at hudson.model.Queue._withLock(Queue.java:1373) at hudson.model.Queue.withLock(Queue.java:1250) at jenkins.model.Jenkins._cleanUpDisconnectComputers(Jenkins.java:3361) at jenkins.model.Jenkins.cleanUp(Jenkins.java:3237) at hudson.lifecycle.UnixLifecycle.restart(UnixLifecycle.java:73) at jenkins.model.Jenkins$24.run(Jenkins.java:4218)Mar 06, 2018 4:50:24 PM jenkins.model.Jenkins _cleanUpShutdownPluginManagerINFO: Stopping
[JIRA] (JENKINS-49956) Kubernetes agent fails to reconnect on master restarts
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-49956 Kubernetes agent fails to reconnect on master restarts Change By: Carlos Sanchez Summary: Kubernetes agent fail fails to reconnect on master restarts Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.