Project

General

Profile

Actions

Bug #4480

closed

When restoring archive (full or groups) dynamic groups are created empty

Bug #4480: When restoring archive (full or groups) dynamic groups are created empty

Added by Vincent MEMBRÉ almost 12 years ago. Updated almost 7 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Config management
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Large
Priority:
0
Name check:
Fix check:
Regression:

Description

When your restore an archive, dynamic groups are restored empty, meaning that Rules won't be generated on those empty groups.

Since dynamic group reload occurs only every 5 minutes, Rules won't be deployed until taht event occurs.

It can be launched manually within the webapp, in Administration -> Settings page or by using the api on the url /api/dyngroup/reload

When groups are restaured and automatic group reloading should be launched before deployment.


Subtasks 1 (0 open1 closed)

Bug #14771: Use of unitialized value error when restoring archiveReleasedNicolas CHARLESActions

Related issues 5 (4 open1 closed)

Related to Rudder - Bug #14758: Accepting a change request on dynamic group, make the group empty leads an invalid policy generation ReleasedNicolas CHARLESActions
Related to Change validation - Bug #14766: When accepting a change request on a group, it's node list should be computed before savingNewActions
Related to Rudder - Architecture #14767: When we accept nodes, dynamic group should be automatically updated at the end of the acceptation, in a synchronized wayNewActions
Related to Rudder - Architecture #7471: Techniques should be reloaded before importing an archiveNewActions
Related to Rudder - Bug #15183: Reload technique library when restoring an archiveNewActions

Updated by François ARMAND almost 12 years ago Actions #1

  • Status changed from New to 8

So, it's less trivial than initially thought:

- 1/ updating dynamic group is done asynchronously, so if we start it before starting promise generation, the result will certainly not be what we want (only partial update of groups ?)
- 2/ but if we issue a not asynchronous dynamic update, it may be long and make the import process even longer.

So, it seems that we want a way to start other things at the end of the dyngroup generation, something "on complete" (that does not exists for now).

Updated by Nicolas CHARLES almost 12 years ago Actions #2

I guess the import time is not that bad, compared to the alternative of having incomplete promises.
Plus, the time of computing groups is in seconds, isn't it ?

Updated by François ARMAND almost 12 years ago Actions #3

Yes, computing groups is quick. But you have to either wait for the next dynamic group generation (by default, 5 min if no luck), or trigger it by hand (need a second action). So it would be far better to have the trigger trigged automatically :)

Updated by Vincent MEMBRÉ almost 12 years ago Actions #4

  • Target version changed from 2.6.11 to 2.6.12

Updated by Vincent MEMBRÉ almost 12 years ago Actions #5

  • Target version changed from 2.6.12 to 2.6.13

Updated by Nicolas CHARLES almost 12 years ago Actions #6

Maybe we could:
- start a dyn update
- wait for x secondes
- deploy

what do you think of it ?

Updated by Vincent MEMBRÉ over 11 years ago Actions #7

  • Target version changed from 2.6.13 to 2.6.14

Updated by Jonathan CLARKE over 11 years ago Actions #8

  • Target version changed from 2.6.14 to 2.6.16

Updated by Jonathan CLARKE over 11 years ago Actions #9

  • Target version changed from 2.6.16 to 2.6.17

Updated by Nicolas PERRON over 11 years ago Actions #10

  • Target version changed from 2.6.17 to 2.6.18

Updated by Matthieu CERDA over 11 years ago Actions #11

  • Target version changed from 2.6.18 to 2.6.19

Updated by Vincent MEMBRÉ over 11 years ago Actions #12

  • Target version changed from 2.6.19 to 2.6.20

Updated by François ARMAND about 11 years ago Actions #13

  • Target version changed from 2.6.20 to 2.10.10

Updated by Vincent MEMBRÉ about 11 years ago Actions #14

  • Target version changed from 2.10.10 to 2.10.11

Updated by Vincent MEMBRÉ almost 11 years ago Actions #15

  • Target version changed from 2.10.11 to 2.10.12

Updated by Vincent MEMBRÉ almost 11 years ago Actions #16

  • Target version changed from 2.10.12 to 2.10.13

Updated by Benoît PECCATTE almost 11 years ago Actions #17

  • Status changed from 8 to New

Updated by Vincent MEMBRÉ almost 11 years ago Actions #18

  • Target version changed from 2.10.13 to 2.10.14

Updated by Vincent MEMBRÉ almost 11 years ago Actions #19

  • Target version changed from 2.10.14 to 2.10.15

Updated by Vincent MEMBRÉ over 10 years ago Actions #20

  • Target version changed from 2.10.15 to 2.10.16

Updated by Vincent MEMBRÉ over 10 years ago Actions #21

  • Target version changed from 2.10.16 to 2.10.17

Updated by Vincent MEMBRÉ over 10 years ago Actions #22

  • Target version changed from 2.10.17 to 2.10.18

Updated by Vincent MEMBRÉ over 10 years ago Actions #23

  • Target version changed from 2.10.18 to 2.10.19

Updated by Vincent MEMBRÉ over 10 years ago Actions #24

  • Target version changed from 2.10.19 to 2.10.20

Updated by Vincent MEMBRÉ about 10 years ago Actions #25

  • Target version changed from 2.10.20 to 2.11.18

Updated by Vincent MEMBRÉ about 10 years ago Actions #26

  • Target version changed from 2.11.18 to 2.11.19

Updated by Vincent MEMBRÉ almost 10 years ago Actions #27

  • Target version changed from 2.11.19 to 2.11.20

Updated by Vincent MEMBRÉ almost 10 years ago Actions #28

  • Target version changed from 2.11.20 to 2.11.21

Updated by Vincent MEMBRÉ over 9 years ago Actions #29

  • Target version changed from 2.11.21 to 2.11.22

Updated by Vincent MEMBRÉ over 9 years ago Actions #30

  • Target version changed from 2.11.22 to 2.11.23

Updated by Vincent MEMBRÉ over 9 years ago Actions #31

  • Target version changed from 2.11.23 to 2.11.24

Updated by Vincent MEMBRÉ over 9 years ago Actions #32

  • Target version changed from 2.11.24 to 308

Updated by Vincent MEMBRÉ over 9 years ago Actions #33

  • Target version changed from 308 to 3.1.14

Updated by Vincent MEMBRÉ over 9 years ago Actions #34

  • Target version changed from 3.1.14 to 3.1.15

Updated by Vincent MEMBRÉ over 9 years ago Actions #35

  • Target version changed from 3.1.15 to 3.1.16

Updated by Vincent MEMBRÉ over 9 years ago Actions #36

  • Target version changed from 3.1.16 to 3.1.17

Updated by Vincent MEMBRÉ about 9 years ago Actions #37

  • Target version changed from 3.1.17 to 3.1.18

Updated by Vincent MEMBRÉ about 9 years ago Actions #38

  • Target version changed from 3.1.18 to 3.1.19

Updated by François ARMAND almost 9 years ago Actions #39

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Effort required set to Large
  • Priority set to 0

Updated by Vincent MEMBRÉ almost 9 years ago Actions #40

  • Target version changed from 3.1.19 to 3.1.20

Updated by Vincent MEMBRÉ almost 9 years ago Actions #41

  • Target version changed from 3.1.20 to 3.1.21

Updated by François ARMAND over 8 years ago Actions #42

  • Priority changed from 0 to 39

Updated by Vincent MEMBRÉ over 8 years ago Actions #43

  • Target version changed from 3.1.21 to 3.1.22

Updated by Benoît PECCATTE over 8 years ago Actions #44

  • Priority changed from 39 to 40

Updated by Vincent MEMBRÉ over 8 years ago Actions #45

  • Target version changed from 3.1.22 to 3.1.23

Updated by Vincent MEMBRÉ over 8 years ago Actions #46

  • Target version changed from 3.1.23 to 3.1.24

Updated by Vincent MEMBRÉ over 8 years ago Actions #47

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 40 to 41

Updated by Vincent MEMBRÉ about 8 years ago Actions #48

  • Target version changed from 3.1.25 to 387

Updated by Vincent MEMBRÉ about 8 years ago Actions #49

  • Target version changed from 387 to 4.1.10

Updated by Vincent MEMBRÉ almost 8 years ago Actions #50

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 41 to 42

Updated by Vincent MEMBRÉ almost 8 years ago Actions #51

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 42 to 43

Updated by Vincent MEMBRÉ almost 8 years ago Actions #52

  • Target version changed from 4.1.12 to 4.1.13

Updated by Vincent MEMBRÉ over 7 years ago Actions #53

  • Target version changed from 4.1.13 to 4.1.14
  • Priority changed from 43 to 44

Updated by Benoît PECCATTE over 7 years ago Actions #54

  • Target version changed from 4.1.14 to 4.1.15

Updated by Vincent MEMBRÉ over 7 years ago Actions #55

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 44 to 45

Updated by Vincent MEMBRÉ over 7 years ago Actions #56

  • Target version changed from 4.1.16 to 4.1.17

Updated by Vincent MEMBRÉ about 7 years ago Actions #57

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 45 to 0

Updated by Vincent MEMBRÉ about 7 years ago Actions #58

  • Target version changed from 4.1.18 to 4.1.19

Updated by Alexis Mousset about 7 years ago Actions #59

  • Target version changed from 4.1.19 to 4.1.20

Updated by Nicolas CHARLES almost 7 years ago Actions #60

it also happens when validating change request, but it's even worse as it does not trigger a dynamic group update - so it lasts much longer in an invalid state

Updated by Nicolas CHARLES almost 7 years ago Actions #61

  • Related to Bug #14758: Accepting a change request on dynamic group, make the group empty leads an invalid policy generation added

Updated by Nicolas CHARLES almost 7 years ago Actions #62

  • Target version changed from 4.1.20 to 5.0.10

Targeting to 5.0, as #14758 take care of the workaround in 4.1

when importing an archive, it should compute node list before saving. This should be synchronized, as others actions can happen at the same time (accept node, change request, etc), and this computation should block loading nodes list in policy generation

Updated by Nicolas CHARLES almost 7 years ago Actions #63

  • Related to Bug #14766: When accepting a change request on a group, it's node list should be computed before saving added

Updated by Nicolas CHARLES almost 7 years ago Actions #64

  • Related to Architecture #14767: When we accept nodes, dynamic group should be automatically updated at the end of the acceptation, in a synchronized way added

Updated by Vincent MEMBRÉ almost 7 years ago Actions #65

  • Target version changed from 5.0.10 to 4.1.22

Updated by Vincent MEMBRÉ almost 7 years ago Actions #66

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ

Updated by Vincent MEMBRÉ almost 7 years ago Actions #67

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/2204

Updated by Vincent MEMBRÉ almost 7 years ago Actions #68

  • Status changed from Pending technical review to Pending release

Updated by Vincent MEMBRÉ almost 7 years ago Actions #70

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.22, 4.3.12 and 5.0.10 which were released today.

Updated by Vincent MEMBRÉ over 6 years ago Actions #71

  • Related to Architecture #7471: Techniques should be reloaded before importing an archive added

Updated by Vincent MEMBRÉ over 6 years ago Actions #72

  • Related to Bug #15183: Reload technique library when restoring an archive added
Actions

Also available in: PDF Atom