Project

General

Profile

Bug #10660

We have no way to know that a Technique is disabled

Added by François ARMAND over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Priority:
0

Description

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)


Related issues

Related to Rudder - Bug #12829: We have no way to know that a Technique is disabled when editing a DirectiveReleased

Associated revisions

Revision a7edede0 (diff)
Added by Raphaël Gauthier over 1 year ago

Fixes #10660: We have no way to know that a Technique is disabled

Revision ee8a3c59 (diff)
Added by Raphaël Gauthier over 1 year ago

Fixes #10660: We have no way to know that a Technique is disabled

History

#1 Updated by François ARMAND over 1 year ago

  • Priority changed from 72 to 0

#2 Updated by Raphael GAUTHIER over 1 year ago

  • Status changed from New to In progress

#3 Updated by Raphael GAUTHIER over 1 year ago

  • Related to Bug #10582: No difference between enabled and disabled directive when filter is active added

#4 Updated by Raphael GAUTHIER over 1 year ago

  • Related to deleted (Bug #10582: No difference between enabled and disabled directive when filter is active)

#5 Updated by Raphael GAUTHIER over 1 year ago

This bug is related to #10582. We should display this information, and do the same for disabled Directives.

#6 Updated by Raphael GAUTHIER over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Raphael GAUTHIER to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1650

#7 Updated by Anonymous over 1 year ago

  • Status changed from Pending technical review to Pending release

#8 Updated by Vincent MEMBRÉ over 1 year 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.

#9 Updated by François ARMAND 6 months ago

  • Related to Bug #12829: We have no way to know that a Technique is disabled when editing a Directive added

Also available in: Atom PDF