-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 1.510 on RHEL5 x86_64
I have 4 similar SSH slave nodes configured. After upgrading to Jenkins 1.510 one of them keeps losing platform labels. In effect all jobs tied to a platform label skip this node.
The node has one manually assigned label. When the issue happens only this one label stays on the node, but all automatically assigned platform labels disappear. To recover from such situation I need:
- Disconnect the node and relaunch it,
- Enter node configuration and press Save button.
After first step (disconnect/relaunch) platform labels do show up, but Jenkins still does not see those labels (reporting no executors with required label available). I need to perform second step (Configure/Save) to make Jenkins actually refresh its labels knowledge. This is an issue I already reported (JENKINS-9586), just in this case it's always reproducible.
Anyway, this solution is not permanent, because after some time platform labels get dropped again and I need to repeat the steps above. I wasn't observing this issue before upgrade to 1.510.
- duplicates
-
-
- Closed
-
[JENKINS-17615] Platform labels disappear from SSH slave node
| Description |
Original:
I have 4 similar SSH slave nodes configured. After upgrading to Jenkins 1.510 one of them keeps losing platform labels. In effect all jobs tied to a platform label skip this node. The node has one manually assigned label. When the issue happens only this one label stays on the node, but all automatically assigned platform labels disappear. To recover from such situation I need: - Disconnect the node and relaunch it, - Enter node configuration and press Save button. After first step (disconnect/relaunch) platform labels do show up, but Jenkins still does not see those labels (reporting no executors with required label available). I need to perform second step (Configure/Save) to make Jenkins actually refresh its labels knowledge. This is an issue I already reported, just in this case it's always reproducible. Anyway, this solution is not permanent, because after some time platform labels get dropped again and I need to repeat the steps above. I wasn't observing this issue before upgrade to 1.510. |
New:
I have 4 similar SSH slave nodes configured. After upgrading to Jenkins 1.510 one of them keeps losing platform labels. In effect all jobs tied to a platform label skip this node. The node has one manually assigned label. When the issue happens only this one label stays on the node, but all automatically assigned platform labels disappear. To recover from such situation I need: - Disconnect the node and relaunch it, - Enter node configuration and press Save button. After first step (disconnect/relaunch) platform labels do show up, but Jenkins still does not see those labels (reporting no executors with required label available). I need to perform second step (Configure/Save) to make Jenkins actually refresh its labels knowledge. This is an issue I already reported ( Anyway, this solution is not permanent, because after some time platform labels get dropped again and I need to repeat the steps above. I wasn't observing this issue before upgrade to 1.510. |
| Link |
New:
This issue is related to |
| Workflow | Original: JNJira [ 148794 ] | New: JNJira + In-Review [ 177202 ] |
| Link |
New:
This issue duplicates |
| Link |
Original:
This issue is related to |
| Assignee | Original: lifeless [ lifeless ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |