Actions
Bug #20704
openAfter removing a block in a technique any new block is non working
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
- create a technique with a method in it
- add a block
- add a method in it
- save
- move the method out
- remove the block
- save : there is an error
- add a new block
-> the new block cannot be edited
Files
Updated by François ARMAND almost 3 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
- Priority changed from 0 to 70
Updated by Elaad FURREEDAN almost 3 years ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Elaad FURREEDAN almost 3 years ago
Can't reproduce
You shouldn't be able to save a technique with a block without component name anyway, but I can't figure it out how you manage to do this.
Updated by Elaad FURREEDAN almost 3 years ago
- Status changed from In progress to New
Updated by Félix DALLIDET almost 3 years ago
Got a similar behaviour while creating a technique from scratch. I added a block and when I wanted to save I got a strange error, and then my technique could not be saved because another "shadow" one was taling its ID. I had to change its name, and when saving, I ended up with both techniques...
See the webapp logs below:
[2022-02-14 14:18:04+0000] INFO policy.generation - [metrics] Xmx:1015 MB nodes:1 (cached:1) rules:4 (enabled:3) techniques:47 (enabled:47) directives:8 (enabled:8) groups:2 (dynamic:2) parameters:2 [2022-02-14 14:18:04+0000] ERROR com.normation.rudder.rest.RestUtils - "Could not create ncf technique <- An error occurred during technique update after files were created for ncf Technique Test bloc with report <- Unexpected: Accumulated: Error when automatically activating technique 'test_bloc_with_report'; cause was: Consistancy: Can not add a technique with id 'test_bloc_with_report' in user library. active technique 'activeTechniqueId=test_bloc_with_report,techniqueCategoryId=ncf_techniques,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration}' is already defined with such a reference technique." [2022-02-14 14:18:04+0000] INFO policy.generation - No node configuration was updated, no policies to write [2022-02-14 14:18:04+0000] DEBUG explain_compliance - Updated node configuration ids: [2022-02-14 14:18:04+0000] INFO policy.generation.timing - Timing summary:
[2022-02-14 14:18:05+0000] INFO policy.generation.timing - Policy generation succeeded in: [2022-02-14 14:18:05+0000] INFO policy.generation.manager - Successful policy update '5' [started 2022-02-14 14:18:04 - ended 2022-02-14 14:18:05] [2022-02-14 14:18:30+0000] ERROR com.normation.rudder.rest.RestUtils - "Could not create ncf technique <- Technique name and ID must be unique. Name 'Test bloc with report' and ID 'test_bloc_with_report' already used, they are case insensitive" [2022-02-14 14:19:06+0000] ERROR com.normation.rudder.rest.RestUtils - "Could not create ncf technique <- Technique name and ID must be unique. Name 'Test bloc with report' and ID 'test_bloc_with_report' already used, they are case insensitive" [2022-02-14 14:19:15+0000] INFO techniques.reader - Reloading technique library, found modified technique(s): ['test_bloc_with_report2': updated (1.0: added)] [2022-02-14 14:19:15+0000] INFO com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'test_bloc_with_report2' in category 'User Techniques (ncf_techniques)' of active techniques library [2022-02-14 14:19:15+0000] INFO com.normation.rudder.services.policies.DeployOnTechniqueCallback - Update Technique library after creating files for ncf Technique Test bloc with report2 [2022-02-14 14:19:15+0000] INFO policy.generation - Start policy generation, checking updated rules [2022-02-14 14:19:15+0000] INFO policy.generation - [metrics] Xmx:1015 MB nodes:1 (cached:1) rules:4 (enabled:3) techniques:48 (enabled:48) directives:8 (enabled:8) groups:2 (dynamic:2) parameters:2 [2022-02-14 14:19:15+0000] INFO policy.generation - No node configuration was updated, no policies to write [2022-02-14 14:19:15+0000] DEBUG explain_compliance - Updated node configuration ids:
Updated by Elaad FURREEDAN almost 3 years ago
Still can't reproduce
Here is the JSON that may cause the bug
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 7.0.1 to 7.0.2
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.0.2 to 7.0.3
- Priority changed from 70 to 68
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.0.3 to 7.0.4
- Priority changed from 68 to 67
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.0.4 to 7.0.5
- Priority changed from 67 to 66
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.0.5 to 7.0.6
- Priority changed from 66 to 65
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.0.6 to 7.0.7
- Priority changed from 65 to 0
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.0.7 to 7.0.8
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.0.8 to 1002
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 1002 to 7.1.7
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.1.7 to 7.1.8
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.1.8 to 7.1.9
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.1.9 to 7.1.10
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.1.10 to 1016
Updated by Alexis Mousset almost 2 years ago
- Target version changed from 1016 to 7.2.5
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.5 to 7.2.6
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.6 to 7.2.7
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.7 to 7.2.8
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.8 to 7.2.9
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.9 to 7.2.10
Updated by Alexis Mousset over 1 year ago
- Target version changed from 7.2.10 to 7.2.11
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.11 to 1046
Updated by Alexis Mousset about 1 year ago
- Target version changed from 1046 to 7.3.8
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.8 to 7.3.9
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.9 to 7.3.10
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.10 to 7.3.11
Updated by Vincent MEMBRÉ 11 months ago
- Target version changed from 7.3.11 to 7.3.12
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.12 to 7.3.13
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.13 to 7.3.14
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 7.3.14 to 7.3.15
Updated by Vincent MEMBRÉ 7 months ago
- Target version changed from 7.3.15 to 7.3.16
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 7.3.16 to 7.3.17
Actions