Bug #13658
closed
User story #16743: Promote a node to relay
There are no eventlogs when converting a node to relay
Description
We don't have any eventlog for converting node to relay, and it also relies on full regeneration (it doesn't detect the change of state), so accepting node won't fix if the clear cache via API failed
so having eventlog would be great, also correctly keeping the state of nodes for each policy generation would be even better
Updated by François ARMAND over 5 years ago
- Project changed from Rudder to Scale-out relay
- Category deleted (
Web - Maintenance)
The problem is that the converstion is not at all a rudder one (it's from script and changing things in base). We can't have an event log for that.
I propose to add that as a feature evolution for the plugin, once we can change a node status to relay (and back) from the UI.
I'm opening a different ticket for the other part which is independant.
Updated by Elaad FURREEDAN about 4 years ago
- Assignee set to Elaad FURREEDAN
- Target version set to 6.1-1.4
Updated by Elaad FURREEDAN about 4 years ago
- Status changed from New to In progress
Updated by Elaad FURREEDAN about 4 years ago
- Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2851
Updated by Elaad FURREEDAN about 4 years ago
- Related to User story #16743: Promote a node to relay added
Updated by Anonymous about 4 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder:rudder|b1acb8c16e475b36670d6fdb00764c972e1a9e37.
Updated by Vincent MEMBRÉ about 4 years ago
- Related to deleted (User story #16743: Promote a node to relay)
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1-1.4 which was released today.