Project

General

Profile

Actions
Copy link

Bug #2263

closed

After rudder-init'ing an existing rudder root server, which had archives of old PIs and PT libs, I get only two enabled PTs and some errors in the logs

Added by Matthieu CERDA almost 13 years ago. Updated over 12 years ago.

Status:
Rejected
Priority:
2
Assignee:
Matthieu CERDA
Category:
Architecture - Code maintenance
Target version:
2.4.0~alpha6
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

After rudder-init'ing an existing rudder root server, which had archives of old PIs and PT libs, I get only two enabled PTs and some errors in the logs:

Log:

15:10:31.300 [main]            INFO  b.l.c.CheckInitUserTemplateLibrary - The user policy template library is not marked as being initialized: adding all policies from reference library...
15:10:40.551 [pool-3-thread-8] INFO  c.n.p.a.service.AgregationService - Finished the agregation in 16858 millisec
15:10:41.396 [main]            WARN  b.l.c.CheckInitUserTemplateLibrary - Some error where encountered during the initialization of the user library 
 -> Error processing /applications 
 -> Error processing /systemSettings 
 -> Error processing /fileDistribution 
 -> Error processing /fileConfiguration 
 -> Error when adding category 'userlib_fileConfiguration' to user library parent category 'UserPolicyTemplateLibraryRoot' 
 -> Auto-archive git failure: not found in git added files: policy-library/userlib_fileConfiguration/category.xml
15:10:42.253 [main]            INFO  bootstrap.liftweb.Boot - Initializing plugin 'Advanced Reporting' [com.normation.plugins.advancedreports.AdvancedReportingPluginDef]
15:10:42.253 [main]            INFO  c.n.p.a.AdvancedReportingPluginDef - loading advancedreporting plugin

Actions
Copy link
 #1

Updated by Matthieu CERDA almost 13 years ago

  • Status changed from New to Discussion
  • Assignee set to Jonathan CLARKE

It looks like it was a collision of uncommited PT's in the /configuration-repository. Should we consider this as a bug or as a side effect of a broken GIT tree ?

Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6

Matthieu CERDA wrote:

It looks like it was a collision of uncommited PT's in the /configuration-repository. Should we consider this as a bug or as a side effect of a broken GIT tree ?

I dunno: it depends what the situation was, what you expected to happen, and what really happened. Could you detail this please?

Actions
Copy link
 #3

Updated by Matthieu CERDA over 12 years ago

I think we should close this, i tried to reproduce it and never managed to make it happen again. I suppose that the test orchestrator was a bit confused.

Actions
Copy link
 #4

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from Discussion to Rejected
  • Assignee changed from Jonathan CLARKE to Matthieu CERDA
Actions
Copy link

Also available in: Atom PDF