Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Blocker
-
Resolution: Unresolved
-
Component/s: vsphere-cloud-plugin, windows-slaves-plugin
-
Environment:Windows 7
-
Similar Issues:
Description
We have a bunch of slave services connected to the master using the Vsphere Cloud/Windows services plugin thru the Local Admin Users. However the Windows Slaves Plugin is not authenticating in to slave machines using NT/LDAP accounts as administrators for bringing up the service. Though the field help tip indicates domain usage, we have not been able to use LDAP/NT accounts to authenticate to slave machines using the plugin. Can we authenticate using NT/LDAP accounts?
_ Provide the name of the Windows user who has the administrative access on this computer, such as 'Administrator'. This information is necessary to start a process remotely.
To specify a domain user, enter values like 'DOMAIN\Administrator'.
(from Windows Slaves Plugin)_
Attachments
Activity
That being said, using the Windows Slaves plugins we are not able to login to NT accounts with a ! (exclamation) symbol in the username
1. DOMAIN \ !username1
2. DOMAIN\username2
From above, 2 works perfect with no issues as in we are able to login to the machine using Windows Slaves Plugin with Vsphere plugin
1 doesn't work and throws the below error. Is it because of the ! in username? Any workarounds are appreciated
ERROR: [2016-10-03 15:46:28] [windows-slaves] Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this.
org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x00000005
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:542)
at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:458)
at org.jinterop.dcom.core.JIComServer.<init>(JIComServer.java:427)
at org.jvnet.hudson.wmi.WMI.connect(WMI.java:59)
at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:208)
at org.jenkinsci.plugins.vSphereCloudLauncher.launch(vSphereCloudLauncher.java:199)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:253)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: rpc.FaultException: Received fault. (unknown)
at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:142)
at rpc.Stub.call(Stub.java:112)
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538)
... 11 more
The NT accounts were not configured to be administrators. We were able to resolve this issue.