[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid

[rejesid...@gmail.com (JIRA)]

rejesi created JENKINS-14856 Slave Registered Remote Controls not identified in Jenkins Selenium Grid Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: selenium Created: 17/Aug/12 8:20 PM Description: I was attempting to rename the newest selenium-server-standalone-*.jar to replace the older one (as per some of the users posts). When I restarted the Jenkins server, the Selenium Grid page shows that the jenkins.nodeName is null for all of the connected remote contols clients (as shown below) {seleniumProtocol=Selenium, browserName=*firefox, maxInstances=5, jenkins.nodeName=} I put everything back the way it was, but this problem still exists, and the process for the hudson.remoting.Launcher of the selenium-server-standalone-*.jar is not running on the agents. Everything says that it should automatically configure and start when the Jenkins server is restarted. Environment: Linux RHEL server Linux Ubuntu slave agent remote client Project: Jenkins Priority: Major Reporter: rejesi

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