Project

General

Profile

Actions

Bug #17421

closed

Add log about node group update failure because of inconsistency

Added by Nicolas CHARLES almost 4 years ago. Updated over 3 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

[2020-05-15 13:25:05+0200] INFO  bootchecks - LDAP and PostgreSQL connection are OK
[2020-05-15 13:25:05+0200] INFO  bootchecks - Check mandatory DIT entries
[2020-05-15 13:25:06+0200] INFO  bootchecks - All the required DIT entries are present in the LDAP directory
[2020-05-15 13:25:06+0200] INFO  bootchecks - Check initialization of User Technique Library
[2020-05-15 13:25:06+0200] INFO  bootchecks - Check that `rudder` global parameter matches default value
[2020-05-15 13:25:06+0200] INFO  bootchecks - Check event log migration format 5 -> 6
[2020-05-15 13:25:06+0200] INFO  bootchecks - Check existence of at least one archive of the configuration
[2020-05-15 13:25:06+0200] INFO  migration - No migration detected by migration script (table 'migrationeventlog' is empty or does not exist)
[2020-05-15 13:25:06+0200] INFO  bootchecks - First full archive of configuration-repository items done
[2020-05-15 13:25:06+0200] INFO  bootchecks - Check rules archive directory in configuration-repository
[2020-05-15 13:25:06+0200] INFO  bootchecks - Creating directory '/var/rudder/configuration-repository/ruleCategories' exists, done
[2020-05-15 13:25:06+0200] INFO  bootchecks - Check for force reload of Techniques library
[2020-05-15 13:25:06+0200] INFO  bootchecks - Flag file '/opt/rudder/etc/force_technique_reload' does not exist, do not Technique library will not be reloaded
[2020-05-15 13:25:06+0200] INFO  bootchecks - Check that system group / directive / rules for Rudder 4.2 are agent-specific
[2020-05-15 13:25:07+0200] INFO  bootchecks - Updating system configuration stored in entry 'nodeGroupId=hasPolicyServer-root,groupCategoryId=SystemGroups,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration': LDIFModifyChangeRecord(dn='nodeGroupId=hasPolicyServer-
root,groupCategoryId=SystemGroups,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration', mods={LDAPModification(type=replace, attr=isSystem, values={'TRUE'})})
[2020-05-15 13:25:07+0200] INFO  bootchecks - Updating system configuration stored in entry 'nodeGroupId=all-nodes-with-cfengine-agent,groupCategoryId=SystemGroups,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration': LDIFModifyChangeRecord(dn='nodeGroupId=all-nod
es-with-cfengine-agent,groupCategoryId=SystemGroups,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration', mods={LDAPModification(type=replace, attr=isSystem, values={'TRUE'})})
[2020-05-15 13:25:07+0200] INFO  bootchecks - Regenerate all ncf techniques
[2020-05-15 13:25:07+0200] INFO  bootchecks - Flag file '/opt/rudder/etc/force_ncf_technique_update' does not exist, do not regenerate ncf Techniques
[2020-05-15 13:25:07+0200] INFO  bootchecks - Resume policy update if it was running before shutdown
[2020-05-15 13:25:07+0200] INFO  bootchecks - Flag file '/opt/rudder/etc/policy-update-running' does not exist, No need to start a new policy update
[2020-05-15 13:25:07+0200] INFO  bootchecks - Trigger policy update if it was requested during shutdown
[2020-05-15 13:25:07+0200] INFO  bootchecks - Create system api token
[2020-05-15 13:25:07+0200] INFO  bootchecks - System api token file created in /var/rudder/run/api-token
[2020-05-15 13:25:07+0200] INFO  bootchecks - Update existing API token to 'RW' autorization level.
[2020-05-15 13:25:07+0200] INFO  bootchecks - Check NashHorn JS engine for warning
[2020-05-15 13:25:07+0200] INFO  bootchecks - Load node compliance cache
[2020-05-15 13:25:07+0200] ERROR scheduled.job - Error when updating dynamic group 'all-nodes-with-cfengine-agent' <- Error when saving update for dynamic group 'All classic Nodes' (all-nodes-with-cfengine-agent) <- Consistancy: The group configuration changed compared to the reference group you want to change the node list for. Aborting to preserve consistency
[2020-05-15 13:25:08+0200] INFO  application - Configured authentication provider(s): [rootAdmin, file]

it does not appear anymore after that


Subtasks 1 (0 open1 closed)

Bug #17476: error about group consistency at upgrade from Rudder 6.0 to 6.1ReleasedNicolas CHARLESActions
Actions #1

Updated by François ARMAND almost 4 years ago

  • Assignee set to Nicolas CHARLES

We should add some debug log to track what modification was prevented in LdapNodeGroupRepository#internalUpdate and reproduce to see if it's a real problem or not.

Actions #2

Updated by Nicolas CHARLES almost 4 years ago

  • Status changed from New to In progress
Actions #3

Updated by Nicolas CHARLES almost 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Elaad FURREEDAN
  • Pull Request set to https://github.com/Normation/rudder/pull/2994
Actions #4

Updated by Nicolas CHARLES almost 4 years ago

  • Subject changed from error about group consistency at upgrade from Rudder 6.0 to 6.1 to Add log about node group update failure because of inconsistency
Actions #5

Updated by Nicolas CHARLES almost 4 years ago

  • Status changed from Pending technical review to Pending release
Actions #6

Updated by Vincent MEMBRÉ almost 4 years ago

This bug has been fixed in Rudder 6.1.0~rc1 which was released today.

Actions #7

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF