Project

General

Profile

Actions

Bug #7751

open

When we delete a relay, all system groups and directive related to this relay are not deleted

Added by Nicolas CHARLES over 8 years ago. Updated 8 months ago.

Status:
New
Priority:
N/A
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Priority:
0
Name check:
Fix check:
Regression:

Description

When we delete a relay, a lot of groups and directive (system) remain. It should even be impossible to delete a relay that as node under it, and only be deletable when it is safe to be so, and in this case purge all system groups/directives/rules linked to it.
This may be done only via an external script (like when we transform a node to relay)


Related issues 2 (1 open1 closed)

Related to Rudder - Bug #7288: Policy does not get deleted when changing relaysNewFrançois ARMANDActions
Related to Rudder - Question #9719: Node deletes are not properly cleaned upResolvedActions
Actions #1

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #2

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #3

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #4

Updated by François ARMAND about 8 years ago

  • Related to Bug #7288: Policy does not get deleted when changing relays added
Actions #5

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #6

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #7

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #8

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.24 to 308
Actions #9

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 308 to 3.1.14
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #11

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #12

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #13

Updated by Janos Mattyasovszky over 7 years ago

  • Related to Question #9719: Node deletes are not properly cleaned up added
Actions #14

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #15

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #16

Updated by Jonathan CLARKE about 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
Actions #17

Updated by Benoît PECCATTE about 7 years ago

  • Priority set to 21
Actions #18

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #19

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #20

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #21

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 21 to 34
Actions #22

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #23

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #24

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #25

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.25 to 387
Actions #26

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 387 to 4.1.10
Actions #27

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #28

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #29

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #30

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #31

Updated by Benoît PECCATTE almost 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #32

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #33

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #34

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.17 to 4.1.18
Actions #35

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions #36

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions #37

Updated by François ARMAND over 5 years ago

  • Target version changed from 4.1.20 to 4.1.21
  • Priority changed from 34 to 35
Actions #38

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions #39

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.22 to 4.1.23
Actions #40

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.23 to 4.1.24
Actions #41

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.24 to 588
  • Priority changed from 35 to 36
Actions #42

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 588 to 5.0.13

still there

Actions #43

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #44

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 36 to 37
Actions #45

Updated by François ARMAND over 4 years ago

  • Project changed from Rudder to Scale-out relay
  • Category deleted (Server components)
  • Assignee set to Elaad FURREEDAN
  • Target version deleted (5.0.15)
  • Effort required set to Very Small
  • Priority changed from 37 to 63

This could be a nice, simple feature to add in scale-out-relay.
Three scenarios:

1/ from the scale-out relay UI:

- list of relays
- delete that relay (the "delete" button should be disabled for relay in that case)

2/ add a "node" deletion hook with the plugin

Deletion already had hooks, but I'm not sure they are for code hook. If no, we need to had them in 6.0.
Then add one for deletion of related feature.

3/ Consider relay as a known case from rudder core and delete related things from rudder core.

This is the simplest and less modular solution: when a node is deleted, look if it is/was a policy server and delete related groups/rule/directives.

Effort very small at least to look and choose at the correct solution.

Actions #46

Updated by Elaad FURREEDAN over 4 years ago

  • Target version set to 5.0-1.2
Actions #47

Updated by Elaad FURREEDAN over 4 years ago

  • Status changed from New to In progress
Actions #48

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0-1.2 to 5.0-1.3
  • Priority changed from 63 to 64
Actions #49

Updated by Elaad FURREEDAN over 4 years ago

  • Status changed from In progress to New
Actions #50

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0-1.3 to 5.0-1.4
  • Priority changed from 64 to 67
Actions #51

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 5.0-1.4 to 7.2
  • Priority changed from 67 to 0
Actions #52

Updated by Alexis Mousset 8 months ago

  • Target version changed from 7.2 to 7.3
Actions

Also available in: Atom PDF