|
|
|
Issue Type:
|
Bug
|
Affects Versions:
|
current |
Assignee:
|
Kohsuke Kawaguchi
|
Components:
|
windows-slaves |
Created:
|
29/Jan/14 8:38 AM
|
Description:
|
When we upgraded from 1.545 to 1.549, we found that we could no longer launch our Windows slaves using the 'DCOM' method. Unfortunately we cannot use JNLP because these are libvirt slaves, and choosing JNLP causes the instances to not even start up (due to issues like JENKINS-8004).
What is happening is this:
- libvirt starts the slave
- Jenkins logs in to the slave
- It then tries to query the Java version
- ... and it all goes pear-shaped from here.
The stack trace is:
So it seems as though the jcifs used is maybe the wrong version (I see that it was patched some time in 2011 to include the 'setTimeout' function). Maybe it was reverted/removed? What could be the cause of this?
|
Project:
|
Jenkins
|
Priority:
|
Critical
|
Reporter:
|
Johan Cronje
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.