Project

General

Profile

Actions

Bug #16198

open

When switching a node managed by the root server to a relay, its policies are not regenerated

Added by Félix DALLIDET over 4 years ago. Updated 11 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very large
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I had a Windows node managed by my root server, I switched it under a relay, trigger inventory run, triggers, relay/root runs.
But the policies of the nodes where not regenerated under the relay ones in the /var/rudder/share of the root server.

I had to trigger manually a policy generation, which ended up with some duplicated policies:

/var/rudder/share# find . | grep zip
./b8dcd41d-be6f-40e5-9b4f-f494fdeda113/share/3d478f22-a138-4973-bb1d-9a36132b63e8/rules/dsc/rudder.zip
./3d478f22-a138-4973-bb1d-9a36132b63e8/rules/dsc/rudder.zip


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #16741: Policies do not seem to be regenerated when a node change its policy serverRejectedActions
Actions #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #2

Updated by Alexis Mousset over 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions #3

Updated by François ARMAND over 4 years ago

It should be taken care of with the next dynamic group update. So it is not "more" broken than it ever was.

The correct, long term solution is:

- we have the full graph (hopefully tree ?) of dependencies in all configuration elements, and in particular we have the reverse dependency from groups to node parameters on which they depends,
- we also have a list of special node properties that are always observed (like policy server),
- when an inventory is updated, we have the exhaustive list of changes compared to previous inventory state,
- with that list and the reverse dependencies, we exactly know what groups/policies were updated and so if a policy generation is needed.

The incorrect, but perhaps more affordable solution:
- make generation node by node. When an inventory arrives, start generation for that node only (and it will check if anything relevant changed).

Actions #4

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #5

Updated by Félix DALLIDET about 4 years ago

  • Related to Bug #16741: Policies do not seem to be regenerated when a node change its policy server added
Actions #6

Updated by Félix DALLIDET about 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Effort required set to Very large
  • Priority changed from 0 to -11
Actions #7

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions #8

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
  • Priority changed from -11 to -10
Actions #9

Updated by Alexis Mousset almost 4 years ago

  • Category changed from Relay server or API to Web - Config management
Actions #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions #11

Updated by Benoît PECCATTE about 3 years ago

  • Target version changed from 797 to 6.1.14
Actions #12

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #13

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #14

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #17

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #18

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #19

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #20

Updated by François ARMAND 8 months ago

  • Target version changed from old 6.1 issues to relocate to 7.3.10
  • Priority changed from -10 to 0
  • Regression set to No
Actions #21

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.3.10 to 7.3.11
Actions #22

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 7.3.11 to 7.3.12
Actions #23

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions #24

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 7.3.13 to 7.3.14
Actions #25

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 7.3.14 to 7.3.15
Actions #26

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 7.3.15 to 7.3.16
Actions #27

Updated by Vincent MEMBRÉ 11 days ago

  • Target version changed from 7.3.16 to 7.3.17
Actions

Also available in: Atom PDF