-
Bug
-
Resolution: Unresolved
-
Major
-
None
It looks as if there is a scenario where vSphereCloud.java Hashtable currentOnline does not get updated as it should.
The nodes will work as they should, then it will fail to launch new nodes.
From the looks of it the method vSphereCloud.canMarkVMOnline() return FALSE on 2nd or 3rd if statement.
I had a quick look and I think the problem is in the vSphereCloudLauncher.postDisconnectVSphereActions() method.
The vSphereCloud vsC = findOurVsInstance(); throws an exception just before the markVMOffline() is called.
It will then never mark the VM as offline and you can never launch a node on that VM again until you restart Jenkins.
[JENKINS-24479] The vSphere cloud will not allow this slave to start at this time.
Assignee | New: Jason Swager [ jswager1 ] |
Workflow | Original: JNJira [ 157460 ] | New: JNJira + In-Review [ 179588 ] |
Assignee | Original: Jason Swager [ jswager1 ] |
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Resolution | Original: Cannot Reproduce [ 5 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |