[
https://issues.jenkins-ci.org/browse/JENKINS-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat resolved JENKINS-3664.
------------------------------
Resolution: Incomplete
No response from the reporter, so resolving as incomplete.
Please reopen if this is still a problem.
> WMI slave instantiation error when using CNAME hostnames
> --------------------------------------------------------
>
> Key: JENKINS-3664
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3664
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: abarbieri
>
> Hello,
> I'm using a Master Hudson v1.304 hosted, Tomcat 6.0.18 and JDK 1.6.0_13 on a
> Windows 2003 Server R2 and I am experiencing 'A duplicate name exists on the
> network.' error when trying to instantiate a Windows slave via the WMI method.
> The configuration for the slave uses the FQDN for the slave host. The slave
> host
> name being used is actually a CNAME rather than the IP Address or the A host
> name entry.
> I believe the source of the problem is actually a JCIFS/SmbTransport issue and
> it seems it could be easily resolved by first performing a DNS lookup and then
> using the returned IP address when constructing the remoteRoot URL.
> Otherwise following what the SSH-Slaves plugin does... by having a Host
> parameter it would be possible to decouple the slave name from its true host
> name or IP address.
> many thanks,
> andrea
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
