Actions
Bug #11702
closedError message when accepting an inventory
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Priority:
0
Name check:
Fix check:
Regression:
Description
When accepting an inventory, I get the following error message - as in screenshot
Can not accept not found inventory with id NodeId(06ca7b97-a727-43d7-9252-7d72d69eb69f)
Inventory is correctly accepted, and there is no error in the logs
2017-11-07 14:59:47] INFO com.normation.rudder.batch.AsyncDeploymentAgent - Successful policy update '18' [started 2017-11-07 14:59:43 - ended 2017-11-07 14:59:47] [2017-11-07 15:00:02] INFO hooks - Executing post-node-acceptance hooks for node with id '06ca7b97-a727-43d7-9252-7d72d69eb69f' [2017-11-07 15:00:02] INFO com.normation.rudder.services.servers.NewNodeManagerImpl - New node accepted and managed by Rudder: 06ca7b97-a727-43d7-9252-7d72d69eb69f [2017-11-07 15:00:02] INFO hooks - Executing post-node-acceptance hooks for node with id '06ca7b97-a727-43d7-9252-7d72d69eb69f' [2017-11-07 15:00:02] INFO com.normation.rudder.batch.UpdateDynamicGroups$LAUpdateDyngroupManager - Dynamic group hasPolicyServer-root: added node with id: [ 06ca7b97-a727-43d7-9252-7d72d69eb69f ], removed: nothing [2017-11-07 15:00:02] INFO com.normation.rudder.batch.UpdateDynamicGroups$LAUpdateDyngroupManager - Dynamic group all-nodes-with-cfengine-agent: added node with id: [ 06ca7b97-a727-43d7-9252-7d72d69eb69f ], removed: nothing [2017-11-07 15:00:02] INFO com.normation.rudder.services.policies.PromiseGenerationServiceImpl - Start policy generation, checking updated rules
it simply seems to be accepting twice the inventory
May or may not be related to #11635
Happens in 4.2, may happen in earlier versions
Files
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.2 to 4.2.3
Updated by Benoît PECCATTE about 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Priority changed from 0 to 50
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.2.3 to 4.2.4
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.2.4 to 4.2.5
- Priority changed from 50 to 48
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.2.5 to 4.2.6
- Priority changed from 48 to 47
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.2.6 to 4.2.7
- Priority changed from 47 to 46
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.2.7 to 414
- Priority changed from 46 to 45
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 414 to 4.3.4
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.3.4 to 4.3.5
- Priority changed from 45 to 44
Updated by François ARMAND about 6 years ago
- Effort required set to Very Small
- Priority changed from 44 to 67
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.3.5 to 4.3.6
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.3.6 to 4.3.7
- Priority changed from 67 to 66
Updated by François ARMAND about 6 years ago
- Related to Bug #12071: Missing key for agent Community with Rudder 4.3 (at least on SLES) added
Updated by François ARMAND about 6 years ago
- Status changed from New to Rejected
- Priority changed from 66 to 0
It doesn't happen anymore, maybe corrected by #12071
Actions