If the next steps happen:
1. User takes off manually a node with a reason "X"
2. The node connection to jenkins is broken. offline reason changes to ChannelTerminated
3. The user change something in the node configuration. (which make the offline reason move to the node and be persistent)
4. The node connection is restored. Offline reason stays ChannelTerminated.
This is in setNode function on Computer model which need to check if the node already have an offline reason and don't override it. (which is quite a problem since Node offlinecause is private...)
Originally reported by galunto, imported from: Update node configuration while offline may override original cause
- assignee:
vlatombe
- status: Closed
- priority: Minor
- component(s): core
- label(s): 2.492.1-fixed
- resolution: Fixed
- resolved: 2024-10-16T13:24:59+00:00
- votes: 0
- watchers: 1
- imported: 2025-11-24
Raw content of original issue
If the next steps happen:
1. User takes off manually a node with a reason "X"
2. The node connection to jenkins is broken. offline reason changes to ChannelTerminated
3. The user change something in the node configuration. (which make the offline reason move to the node and be persistent)
4. The node connection is restored. Offline reason stays ChannelTerminated.
This is in setNode function on Computer model which need to check if the node already have an offline reason and don't override it. (which is quite a problem since Node offlinecause is private...)
If the next steps happen:
1. User takes off manually a node with a reason "X"
2. The node connection to jenkins is broken. offline reason changes to ChannelTerminated
3. The user change something in the node configuration. (which make the offline reason move to the node and be persistent)
4. The node connection is restored. Offline reason stays ChannelTerminated.
This is in setNode function on Computer model which need to check if the node already have an offline reason and don't override it. (which is quite a problem since Node offlinecause is private...)
Originally reported by galunto, imported from: Update node configuration while offline may override original cause
Raw content of original issue