Project

General

Profile

Actions
Copy link

Bug #16377

closed

Bug when recreating a directive with the exact same name as another one

Added by Félix DALLIDET almost 5 years ago. Updated about 1 year ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
old 6.1 issues to relocate
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I had a directive made under a given technique, which was used in a rule (created via API).
It happens that it was made under the wrong technique, so I tried to create a new one, using the expected technique.
Of course, it did not work since their was already a directive with the same name.

I deleted the old one, created the new one and.... generation brakes.
In the rule page, the old directive is still listed as "in error" under the rule.
See the screenshot below.

Files

directive_error.png (32.4 KB) directive_error.png Félix DALLIDET, 2019-12-09 12:11
Actions
Copy link
 #1

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #3

Updated by François ARMAND over 4 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 47
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
  • Priority changed from 47 to 46
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
  • Priority changed from 46 to 45
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.20 to 797
  • Priority changed from 45 to 44
Actions
Copy link
 #7

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 797 to 6.1.14
  • Priority changed from 44 to 43
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #16

Updated by François ARMAND about 1 year ago

  • Status changed from New to Rejected
  • Priority changed from 43 to 0
  • Regression set to No

I was not able to reproduce (I used the UI for deletion of techniques).
Clearly, the problem was that when the directive was deleted, it was not correctly removed from the rule. That's what broke the generation.

The workaround is to go to the rule, remove the "unknown" directive, save the rule.

I'm closing it, but we will try to understand the "why directive was not removed in rule" part if it happens again.

Actions
Copy link

Also available in: Atom PDF