-
Bug
-
Resolution: Duplicate
-
Major
-
None
We experienced that one of nine jenkins slave/worker nodes is forgotten on every jenkins restart.
Manually re-adding nodes again and again is very cumbersome - especially since there is no API for that.
We would appreciate help for deeper debugging this issue.
- duplicates
-
JENKINS-22525 "incompatible InnerClasses attribute" error in IBM J9 VM
-
- Resolved
-
[JENKINS-22175] slave nodes are forgotten
Attachment | New: System Information [Jenkins].html [ 25548 ] |
Description |
Original:
We experienced that sometimes one of nine jenkins slave/worker nodes is forgotten - mostly after jenkins restart. Manually re-adding nodes again and again is very cumbersome - especially since there is no API for that. We would appreciate help for deeper debugging this issue. |
New:
We experienced that one of nine jenkins slave/worker nodes is forgotten on every jenkins restart. Manually re-adding nodes again and again is very cumbersome - especially since there is no API for that. We would appreciate help for deeper debugging this issue. |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 154254 ] | New: JNJira + In-Review [ 194846 ] |
Further analysis showed that config.xml still contained the missing slave entry, but jenkins consistently ignored the first <slave>...</slave> part for its live data.