-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Platform: All, OS: All
Hudson's "System Configuration" view allows to enter Slaves without names, and
this easily screws the whole Hudson's, killing all the executors (they are
marked in red as DEAD, and even changing the amount of executors configured.
Afterwards, the Hudson needs to be restarted to restore its operations.
There are some exceptions as well:
1. After the slave with non name is added:
Exception in thread "Executor #1 for " at
hudson.model.Hudson.removeComputer(Hudson.java:294)
at hudson.model.Computer.removeExecutor(Computer.java:166)
at hudson.model.Executor.run(Executor.java:38)
java.lang.NullPointerException
at hudson.model.Queue$JobOffer.isNotExclusive(Queue.java:107)
at hudson.model.Queue.choose(Queue.java:366)
at hudson.model.Queue.pop(Queue.java:253)
at hudson.model.Executor.run(Executor.java:44)
2. When trying to delete a Slave without name.
Exception in thread "Executor #2 for " java.lang.IllegalStateException: Trying
to remove unknown computer: hudson.model.Computer@12cd8d4
at hudson.model.Hudson.removeComputer(Hudson.java:294)
at hudson.model.Computer.removeExecutor(Computer.java:166)
at hudson.model.Executor.run(Executor.java:38)