Bug #22525
closedDirectives applied twice don't show in rule details (they should be skipped)
Added by Nicolas CHARLES over 1 year ago. Updated 7 months ago.
Description
but it does appears as skipped on the node compliance page
in the rule page: per directive nothing
per node nothing
Files
clipboard-202303231725-lmhyd.png (64.2 KB) clipboard-202303231725-lmhyd.png | Nicolas CHARLES, 2023-03-23 17:25 | ||
clipboard-202303231727-slfpe.png (64.7 KB) clipboard-202303231727-slfpe.png | Nicolas CHARLES, 2023-03-23 17:27 | ||
clipboard-202303231727-6tyrs.png (37.4 KB) clipboard-202303231727-6tyrs.png | Nicolas CHARLES, 2023-03-23 17:27 |
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.6 to 7.2.7
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.7 to 7.2.8
Updated by François ARMAND over 1 year ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- UX impact set to It bothers me each time
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 99
Updated by Elaad FURREEDAN over 1 year ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Nicolas CHARLES over 1 year ago
- Related to Bug #18931: No skipped directives on Rule screen after parent ticket added
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.8 to 7.2.9
- Priority changed from 99 to 97
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.9 to 7.2.10
- Priority changed from 97 to 96
Updated by Alexis Mousset over 1 year ago
- Target version changed from 7.2.10 to 7.2.11
- Priority changed from 96 to 95
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.2.11 to 1046
- Priority changed from 95 to 93
Updated by Alexis Mousset about 1 year ago
- Target version changed from 1046 to 7.3.8
- Priority changed from 93 to 92
Updated by Elaad FURREEDAN about 1 year ago
- Priority changed from 92 to 91
Work in progess here: https://github.com/ElaadF/rudder/commit/c64c6dced693d14b9e5a3912132266feef98ed19
Updated by Elaad FURREEDAN about 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/5132
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.8 to 7.3.9
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.9 to 7.3.10
Updated by François ARMAND about 1 year ago
- Related to Bug #15125: Rule shown as "Mixed" whereas applied to one audit node and one (skipped) enforce directive added
Updated by Elaad FURREEDAN about 1 year ago
- Status changed from Pending technical review to In progress
- Assignee changed from Nicolas CHARLES to Elaad FURREEDAN
- Priority changed from 91 to 90
I'm taking over this issue!
Updated by Vincent MEMBRÉ 12 months ago
- Target version changed from 7.3.10 to 7.3.11
- Priority changed from 90 to 89
Updated by Clark ANDRIANASOLO 10 months ago
- Assignee changed from Elaad FURREEDAN to Nicolas CHARLES
- Priority changed from 89 to 87
Updated by Clark ANDRIANASOLO 10 months ago
- Assignee changed from Nicolas CHARLES to Elaad FURREEDAN
Updated by Clark ANDRIANASOLO 10 months ago
- Priority changed from 87 to 86
We need to :
- add the information to the current API endpoint whenever the directive is skipped (ideally also all other API endpoints for compliance)
- display the skipped badge from this information
Updated by Clark ANDRIANASOLO 10 months ago
- Related to Architecture #23656: Rewrite Nodes compliance table in Elm added
Updated by Clark ANDRIANASOLO 10 months ago
(Note : in 7.3 the node compliance tree shows the "skipped" badge, but it has also been rewritten in Elm since 8.0 in the issue https://issues.rudder.io/issues/23656 where it disappears)
Updated by Clark ANDRIANASOLO 10 months ago
- Assignee changed from Elaad FURREEDAN to Clark ANDRIANASOLO
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.11 to 7.3.12
Updated by Vincent MEMBRÉ 9 months ago
- Target version changed from 7.3.12 to 7.3.13
- Priority changed from 86 to 85
Updated by Vincent MEMBRÉ 9 months ago
- Target version changed from 7.3.13 to 7.3.14
- Priority changed from 85 to 84
Updated by Clark ANDRIANASOLO 8 months ago
Work in progess here: https://github.com/clarktsiory/rudder/commit/43da87232414f2e0698f97f781546d298403095f
Updated by Clark ANDRIANASOLO 8 months ago
Work in progess here: https://github.com/clarktsiory/rudder/commit/f805f0e1c4fe659650ce5ffe7547622a136ee96f
Updated by Clark ANDRIANASOLO 8 months ago
Work in progess here: https://github.com/clarktsiory/rudder/commit/a6da78b91bd441e3fb3c1c46e0eb3ef47c4870fd
Updated by Clark ANDRIANASOLO 7 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request changed from https://github.com/Normation/rudder/pull/5132 to https://github.com/Normation/rudder/pull/5600
Updated by Clark ANDRIANASOLO 7 months ago
- Status changed from Pending technical review to In progress
Updated by Clark ANDRIANASOLO 7 months ago
- Status changed from In progress to Pending technical review
Updated by Clark ANDRIANASOLO 7 months ago
- Assignee changed from François ARMAND to Elaad FURREEDAN
Updated by Clark ANDRIANASOLO 7 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|c99e3115f13aaa936c8301e72d95d182803173ba.
Updated by François ARMAND 7 months ago
- Related to Bug #24097: Skipped directive does not show in node compliance tree added
Updated by François ARMAND 7 months ago
- Fix check changed from To do to Checked
Works well for rules, it still needs to be corrected for nodes (see #24097)
Updated by Vincent MEMBRÉ 7 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.14, 8.0.8 and 8.1.1 which were released today.