• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: vsphere-cloud-plugin
• Labels:

  None

[JENKINS-55789] Document expected bug 23212 - idle timeout overrides boot

Josiah Eubank created issue - 2019-01-26 00:40

pjdarton made changes - 2019-09-24 12:16

Link

New: This issue is related to JENKINS-23212 [ JENKINS-23212 ]

pjdarton made changes - 2019-09-24 12:17

Description

Original: This 2014 comment is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect."   However, I cannot find this documented anywhere and it should be on the plugin page – or fixed.  Idle timeout should not start counting down until after the connect is complete.

New: [This comment|https://issues.jenkins-ci.org/browse/JENKINS-23212?focusedCommentId=204868&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-204868] is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect." However, I cannot find this documented anywhere and it should be on the plugin page – or fixed.  Idle timeout should not start counting down until after the connect is complete.

pjdarton made changes - 2019-09-24 12:17

Description

Original: [This comment|https://issues.jenkins-ci.org/browse/JENKINS-23212?focusedCommentId=204868&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-204868] is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect." However, I cannot find this documented anywhere and it should be on the plugin page – or fixed.  Idle timeout should not start counting down until after the connect is complete.

New: [This comment from JENKINS-23212|https://issues.jenkins-ci.org/browse/JENKINS-23212?focusedCommentId=204868&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-204868] is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect." However, I cannot find this documented anywhere and it should be on the plugin page – or fixed.  Idle timeout should not start counting down until after the connect is complete.