Project

General

Profile

Bug #10480

Bug #10448: No generation triggered at the end of installation

No generation triggered on technique reload if it was partially loaded before

Added by Nicolas CHARLES about 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:
0

Description

In some race conditions, if technique reload was partially done and interrupted (by rudder-init for instance), at next restart, the web interface fails to completly reload the techniques (some are already there), and don't trigger the generation
We so have a semi-working system.

Associated revisions

Revision 9309d540 (diff)
Added by Nicolas CHARLES about 1 year ago

Fixes #10480: No generation triggered on technique reload if it was partially loaded before

Revision 772df92b (diff)
Added by Nicolas CHARLES about 1 year ago

Fixes #10480: No generation triggered on technique reload if it was partially loaded before

History

#1 Updated by Nicolas CHARLES about 1 year ago

error is
first log file

/var/log/rudder/webapp/2017_03_22.stderrout.log.110159129:[2017-03-22 11:01:47] INFO  bootchecks - Check initialization of User Technique Library
/var/log/rudder/webapp/2017_03_22.stderrout.log.110159129:[2017-03-22 11:01:47] INFO  application - The Active Technique library is not marked as being initialized: adding all policies from reference library...

second log file

[2017-03-22 11:02:36] INFO  bootchecks - Check initialization of User Technique Library
[2017-03-22 11:02:36] INFO  application - The Active Technique library is not marked as being initialized: adding all policies from reference library...
[2017-03-22 11:02:40] WARN  application - Some error where encountered during the initialization of the user library
-> Error when adding Technique 'clockConfiguration' into user library category 'misc'
-> Error when adding Technique 'fstabConfiguration' into user library category 'systemManagement'
-> Error when adding Technique 'hostsConfiguration' into user library category 'networking'
-> Error when adding Technique 'fileAlterationMonitoring' into user library category 'security'
-> Error when adding Technique 'sudoParameters' into user library category 'userManagement'
-> Error when adding Technique 'sshKeyDistribution' into user library category 'remoteAccess'
-> Error when adding Technique 'sshConfiguration' into user library category 'remoteAccess'
-> Can not add a technique with id sshConfiguration in user library. active technique activeTechniqueId=1b708e34-1fb6-4ecc-b9d1-91b056b5ea32,techniqueCategoryId=remoteAccess,techniqueCategoryId=systemSettings,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration is already defined with such a reference technique.

#2 Updated by Nicolas CHARLES about 1 year ago

  • Target version set to 3.1.19

this may happen in 3.1 also

#3 Updated by Nicolas CHARLES about 1 year ago

  • Status changed from New to In progress

#4 Updated by Nicolas CHARLES about 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1607

#5 Updated by Nicolas CHARLES about 1 year ago

  • Status changed from Pending technical review to Pending release

#6 Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released
  • Priority set to 0

This bug has been fixed in Rudder 3.1.19, 4.0.4 and 4.1.1 which were released today.

Also available in: Atom PDF