-
Bug
-
Resolution: Fixed
-
Major
-
None
-
yet-another-docker-plugin:rc38
remoting:3.11
-
-
Remoting 3.30, Jenkins 2.176
Given a container has been started via the yet-another-docker-plugin (and possibly any other cloud provider), and leaving the JNLP process to reconnect (ie, no --no-reconnect flag)
Eventually, after a Jenkins master restart, the JNLP process is receiving a 404 on requests to
slaveJnlpURL
with the remoting Launcher class retrying forever (haven't fond the cause for the slave removal).
This loop wont be exited, leading to resource extarvation.
A possible solution would be throwing a FileNotFoundException under a 404, at Launcher.java and adding a new exception handler at the same class (as that 404 will be not recoverable)
- causes
-
JENKINS-57713 Cloud agent provisioning errors due to Remoting behaviour change
-
- Resolved
-
- links to
[JENKINS-46515] Launcher will retry connections forever under some irrecoverable status
Summary | Original: Launcher will retry connections forever under some invalid circumstances | New: Launcher will retry connections forever under some irrecoverable status |
Epic Link | New: JENKINS-38833 [ 175240 ] |
Assignee | New: Javier Delgado [ witokondoria ] |
Remote Link | New: This issue links to "PR-193 (Web Link)" [ 17609 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Released As | New: Remoting 3.30 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Closed [ 6 ] |
Released As | Original: Remoting 3.30 | New: Remoting 3.30, Jenkins 2.176 |
Labels | New: lts-candidate |
Labels | Original: lts-candidate |