-
Bug
-
Resolution: Fixed
-
Critical
-
Software version: Jenkins ver. 1.635
Possibly related plug-in: Windows Slaves Plugin
Java version: 1.8.0_66
Operating system: Windows Server 2008 R2
When performing a node name rework, it is possible (partially?) overwrite a node with another one simply by renaming an existing node.
Steps to reproduce:
- Create a node named foo
- Create another node named bar
- Go to the bar node configuration
- Rename it to foo and press Save
Expected results:
- An error message.
Actual results:
- Node bar replaces foo without any notice
- Things start to behave wacky: build starts to fail without a reason (see attached edited log, Jenkins-BuildBreakageAfterNodeRename.txt
When attempting to create a new node with the same name as an existing node (rather than editing), an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400. I'd propose throwing this same error upon trying to rename a node over another existing node.
Fixed in PR #1949.