-
Bug
-
Resolution: Fixed
-
Blocker
-
Jenkins LTS 2.50.3 with default plugins installed
-
-
2.174
Renaming an agent does not persist across restarts, and jenkins loads back the old agent as well as the new agent. The root issue seems to be that the directory under ${JENKINS_HOME}/nodes/<agent> is left untouched on a rename, and is left alongside the one created for the new agent.
Steps to reproduce:
- Create a new agent
- Configure -> Rename the agent and click Save
- Restart Jenkins to see the old agent appear
This caused several issues where the old and new agents were trying to connect to the same host, causing build issues
This is reproducible on several jenkins LTS versions (2.107, 2.138, 2.150), so I'm not sure when it was introduced.
- is caused by
-
JENKINS-33780 Listener for slave creation/deletion/update.
-
- Resolved
-
- relates to
-
JENKINS-27565 Nodes can be removed as idle before the assigned tasks have started
-
- Closed
-
- links to
[JENKINS-56403] Renaming jenkins agents persists previously named agent on restart
Summary | Original: Renaming jenkins agents persists old agents alongside old agents on restart | New: Renaming jenkins agents persists previously named agent on restart |
Labels | New: core jenkins |
Link |
New:
This issue relates to |
Link |
New:
This issue is caused by |
Remote Link | New: This issue links to "PR 3925 (Web Link)" [ 22451 ] |
Assignee | New: Anish Dangi [ adangi ] |
oleg_nenashev jglick