Project

General

Profile

Actions

Bug #6575

closed

When we accept a new node, we have two promises generation instead of one

Added by Nicolas CHARLES almost 6 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
2
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

When accepting a new node, we have two promises generation: one for the dynamic group update, and one for the node acceptation

Webapp log says:

[2015-04-13 15:36:20] WARN  com.normation.rudder.repository.xml.GitNodeGroupArchiverImpl - Auto-archive git failure: not found in git added files: 'groups/uuid1/uuid2.xml'. You can safelly ignore that warning if the file was already existing in Git and was not modified by that archive.
[2015-04-13 15:36:20] WARN  com.normation.rudder.repository.xml.GitNodeGroupArchiverImpl - Auto-archive git failure: not found in git added files: 'groups/uuid1/uuid3.xml'. You can safelly ignore that warning if the file was already existing in Git and was not modified by that archive.
[2015-04-13 15:36:20] INFO  com.normation.rudder.batch.UpdateDynamicGroups$LAUpdateDyngroupManager - Dynamic group hasPolicyServer-uuid4: added node with id: [ uuid5 ], removed: nothing
[2015-04-13 15:36:20] INFO  com.normation.rudder.batch.UpdateDynamicGroups$LAUpdateDyngroupManager - Dynamic group uuid6: added node with id: [ uuid7 ], removed: nothing
[2015-04-13 15:36:20] INFO  com.normation.rudder.batch.UpdateDynamicGroups$LAUpdateDyngroupManager - Dynamic group uuid8c: added node with id: [ uuid ], removed: nothing
[2015-04-13 15:36:20] INFO  com.normation.rudder.services.policies.DeploymentServiceImpl - Start policy generation, checking updated rules
[2015-04-13 15:36:20] INFO  com.normation.rudder.batch.AsyncDeploymentAgent - One automatic policy update process is already pending, ignoring new policy update request
[2015-04-13 15:36:21] INFO  com.normation.rudder.services.policies.nodeconfig.NodeConfigurationServiceImpl - Configuration of following nodes were updated, their promises are going to be written: [list of nodes]

Happens at least in 2.11


Related issues

Related to Rudder - Bug #10446: Policy validation failsReleasedFrançois ARMANDActions
Actions #1

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.11.11 to 2.11.12
Actions #2

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from New to Pending technical review
  • Assignee set to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/863
Actions #3

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #5

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.11.12 to 2.11.11
Actions #6

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.11 and 3.0.5 which were released today.

Actions #7

Updated by Nicolas CHARLES about 4 years ago

  • Related to Bug #10446: Policy validation fails added
Actions

Also available in: Atom PDF