Project

General

Profile

Actions

Architecture #19127

open

Overridden directives in the same rule are missing before a full regeneration

Added by François ARMAND over 3 years ago. Updated 10 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

Description

So, in #19114, we had missing directive because of a bug.
Now, we have the correct behavior, but only after a full regeneration if the added directive doesn't change actual configuration.

This is because is the added directive is skipped everywhere, the effective configuration doesn't change on any nodes, so the first step of policy generation that looks if it is necessary to compute new generation say "no, it isn't", then we don't have new expected configuration, and it's expected configuration that are used to check if directives are skipped.
That's all because we don't really apply directives to rule, we apply directives to nodes (with a lot of graphe resolution in the middle, involving rules and groups).

Correcting that one would mean that we need to change expected configuration in a case when it's actually not needed (because, well, they don't change) and would lead to poetentially long computation for nothing. I'm not sure about what to do.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #19114: Overridden directives in the same rule are missing (not even "skipped")ReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND over 3 years ago

  • Related to Bug #19114: Overridden directives in the same rule are missing (not even "skipped") added
Actions #2

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.2.5 to 6.2.6
Actions #3

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.2.6 to 6.2.7
Actions #4

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.2.7 to 6.2.8
Actions #5

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.2.8 to 6.2.9
Actions #6

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.2.9 to 6.2.10
Actions #7

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.2.10 to 6.2.11
Actions #8

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.11 to 6.2.12
Actions #9

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.12 to 6.2.13
Actions #10

Updated by François ARMAND over 2 years ago

  • Tracker changed from Bug to Architecture
  • Priority deleted (0)
Actions #11

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.13 to 6.2.14
Actions #12

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.14 to 6.2.15
Actions #13

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.15 to 6.2.16
Actions #14

Updated by Alexis Mousset almost 2 years ago

  • Target version changed from 6.2.16 to 6.2.17
Actions #15

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.17 to 997
Actions #16

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 997 to 6.2.18
Actions #17

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.18 to 6.2.19
Actions #18

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.19 to 6.2.20
Actions #19

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.20 to old 6.2 issues to relocate
Actions #20

Updated by Alexis Mousset 12 months ago

  • Target version changed from old 6.2 issues to relocate to 7.2.11
  • Regression set to No
Actions #21

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 7.2.11 to 1046
Actions #22

Updated by Alexis Mousset 10 months ago

  • Target version changed from 1046 to Ideas (not version specific)
Actions

Also available in: Atom PDF