• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: core
• Labels:

  • newbie-friendly

[JENKINS-35272] Launcher's afterDisconnect() method is called twice

Giuseppe Landolfi created issue - 2016-06-01 16:08

Giuseppe Landolfi made changes - 2016-06-01 16:08

Component/s		New: core [ 15593 ]
Component/s	Original: vsphere-cloud-plugin [ 16104 ]

Giuseppe Landolfi made changes - 2016-06-01 16:09

Description

Original: The call to r.getExecutor().getOwner().disconnect() in vSphereCloudSlave causes vSphereCloudLauncher's afterDisconnect() to be called twice, on separate threads. This means, for instance, that a VM configured to shutdown and revert after a disconnect will do so twice. This appears to be an issue with Jenkins itself. A temporary fix on my side is the use of an AtomicBoolean to prevent the afterDisconnect from executing its logic twice. Would this be considered an acceptable patch?

New: When a DumbSlave disconnects, the launcher's afterDisconnect() is called twice. This means, for instance, that a VM configured to shutdown and revert after a disconnect will do so twice.

Giuseppe Landolfi made changes - 2016-06-01 16:10

Link

New: This issue duplicates JENKINS-22740 [ JENKINS-22740 ]

R. Tyler Croy made changes - 2016-07-25 23:52

Workflow

Original: JNJira [ 171514 ]

New: JNJira + In-Review [ 184339 ]

Oleg Nenashev made changes - 2017-03-13 15:48

Labels

New: newbie-friendly

Vyshakh Nambiar made changes - 2017-10-16 15:40

Assignee

New: Vyshakh Nambiar [ vn17 ]

Vyshakh Nambiar made changes - 2017-10-16 15:57

Assignee

Original: Vyshakh Nambiar [ vn17 ]