Project

General

Profile

Actions

Bug #17862

closed

error when importing techniques and running reload-techniques in 6.1

Added by Nicolas CHARLES almost 4 years ago. Updated 5 months ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Severity:
Minor - inconvenience | misleading | easy 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 unziped a full archive in /var/rudder/configuration-repository/ and executed

# rudder server reload-techniques
error: Could not reload techniques from files
Error: An error occured when updating the Technique library from file system
cause:Accumulated: Error when automatically activating technique 'NTP_configuration'; cause was: Consistancy: Can not add a technique with id 'NTP_configuration' in user library. active technique 'activeTechniqueId=0075285c-8da9-4fc9-be46-3a9bf03f5f29,techniqueCategoryId=ncf_techniques,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration}' is already defined with such a reference technique.

it does work but this is surprising
webapp logs says
[2020-06-29 12:55:45+0000] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically addi
ng technique 'Desactivate_Telnet' in category 'User Techniques (ncf_techniques)' of active techniques library
[2020-06-29 12:55:45+0000] INFO  com.normation.rudder.services.policies.DeployOnTechniqueCallback - Technique library re
loaded from REST API
[2020-06-29 12:55:45+0000] ERROR com.normation.rudder.rest.v1.RestTechniqueReload - An error occured when updating the Technique library from file system <- Accumulated: Error when automatically activating technique 'NTP_configuration'; cause was: Consistancy: Can not add a technique with id 'NTP_configuration' in user library. active technique 'activeTechniqueId=0075285c-8da9-4fc9-be46-3a9bf03f5f29,techniqueCategoryId=ncf_techniques,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration}' is already defined with such a reference technique.


Related issues 3 (2 open1 closed)

Related to Rudder - Bug #17690: When creating a user technique with restore archive, policy are not correctly regeneratedNewActions
Related to Rudder - Bug #17774: Duplicate category name error when saving a new user techniqueReleasedVincent MEMBRÉActions
Related to Rudder - Bug #20520: Error while importing ncf techniques using the restore from latest commit featureNewActions
Actions #1

Updated by Nicolas CHARLES almost 4 years ago

more log don't show anything.
however importing archives don't import the techniques, and then the same error happens when doing the reload-techniques
tehcniques all appears, but are disabled.
Enabling them cause the following error for some of them:

Can not find dependencies. Can not build tree of dependencies for Technique ActiveTechniqueId(5541bf22-f18f-47fe-8339-de88b4fbf4e6)

Actions #2

Updated by Nicolas CHARLES almost 4 years ago

  • Related to Bug #17690: When creating a user technique with restore archive, policy are not correctly regenerated added
Actions #3

Updated by François ARMAND almost 4 years ago

  • Related to Bug #17774: Duplicate category name error when saving a new user technique added
Actions #4

Updated by Nicolas CHARLES almost 4 years ago

method techniqueDependencies returns empty on some techniques

Actions #5

Updated by Nicolas CHARLES almost 4 years ago

For the error message in the technique tree, the method tree in TechniqueTree is called twice: once with switchStatusFilter is DontCare (which succeed) and one with switchStatusFilter is OnlyEnableable (which returns empty). The second one returns nothing, because it already disabled

Actions #6

Updated by François ARMAND almost 4 years ago

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

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.2 to 6.1.3
Actions #8

Updated by François ARMAND over 3 years ago

  • Target version changed from 6.1.3 to 6.1.4
Actions #9

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.4 to 6.1.5
Actions #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.5 to 6.1.6
  • Priority changed from 32 to 31
Actions #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.6 to 6.1.7
Actions #12

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.7 to 6.1.8
  • Priority changed from 31 to 30
Actions #13

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.8 to 6.1.9
Actions #14

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.9 to 6.1.10
  • Priority changed from 30 to 29
Actions #15

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.10 to 6.1.11
Actions #16

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.11 to 6.1.12
Actions #17

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.12 to 6.1.13
  • Priority changed from 29 to 28
Actions #18

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.13 to 6.1.14
Actions #19

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
  • Priority changed from 28 to 27
Actions #20

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #21

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #22

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #23

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #24

Updated by Benoît PECCATTE over 2 years ago

  • Category set to Web - Config management
Actions #25

Updated by François ARMAND about 2 years ago

  • Related to Bug #20520: Error while importing ncf techniques using the restore from latest commit feature added
Actions #26

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #27

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #28

Updated by Vincent MEMBRÉ almost 2 years ago

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

Updated by François ARMAND 5 months ago

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

This was changed in the past somehow.

Actions

Also available in: Atom PDF