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

[eub.kansas19@gmail.com (JIRA)]

Josiah Eubank created an issue

Jenkins / JENKINS-55789 Document expected bug 23212 - idle timeout overrides boot Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2019-01-26 00:40 Priority: Minor Reporter: Josiah Eubank 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. Add Comment

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

[pjdarton@gmail.com (JIRA)]

pjdarton updated an issue

Jenkins / JENKINS-55789 Document expected bug 23212 - idle timeout overrides boot

Change By: pjdarton [ This 2014 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.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[pjdarton@gmail.com (JIRA)]

pjdarton updated an issue

Jenkins / JENKINS-55789 Document expected bug 23212 - idle timeout overrides boot Change By: pjdarton

[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.

Add Comment