We have no way to know that a Technique is disabled
With my colleage, we spent a lot of time to try to understand why a directive was not applied on Nodes. The generation was ok, all other directive were getting their directory in /var/rudder/share/xxx/ for the node, but not that one. Not even a warning message, nothing.
So, it happens that the Technique was disabled. Before 4.0, there was a visual indication of that state in the directive tree (Technique name in light grey italic), but that information was removed in 4.0. And the only way to know that the Technique is disabled is to go to the Technique management page, something that nobody does (and I actually found the problem by looking at the LDAP raw datas, not by going in that page).
We must AT LEAST apply again the disable style that was in 3.1. The solution could be better, but that one is simple.
Severity is set to Major because it is a regression (plus the workaround is not at all easy to find, and for the user who doesn't know that the technique is disable, Rudder seems very broken)
Updated by Vincent MEMBRÉ over 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.5 and 4.1.2 which were released today.
- 4.0.5: Announce Changelog
- 4.1.2: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/