Actions
Bug #6575
closedWhen we accept a new node, we have two promises generation instead of one
Status:
Released
Priority:
2
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
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
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.11.11 to 2.11.12
Updated by Nicolas CHARLES over 9 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
Updated by Nicolas CHARLES over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|366c83d56ac2ebd16b4482e2cfb7a0134e55417c.
Updated by Nicolas CHARLES over 9 years ago
Applied in changeset rudder|35c0a825677a12ac2085b867de21bbff3659e067.
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.11.12 to 2.11.11
Updated by Vincent MEMBRÉ over 9 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.
- Announcement 2.11
- Changelog 2.11 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Nicolas CHARLES almost 8 years ago
- Related to Bug #10446: Policy validation fails added
Actions