Actions
User story #9676
closedAn agent run with initial promises should send its inventory more often
Status:
Released
Priority:
N/A
Assignee:
Category:
System techniques
Target version:
Effort required:
Name check:
Fix check:
Regression:
Description
If an agent has its initial promises it means it cannot update. (as soon as the second run)
If it cannot update, it means the server doesn't know it, or the server is not yet configured. (unless there is a network problem)
If the server doesn't know it, it means it hasn't been accepted.
If it hasn't been accepted it means the user has not yet clicked on it or that the inventory has not yet been received.
If we run the inventory more often on initial promises, it will be sent faster if the user doesn't do it after configuring the server. And the node will be configured faster.
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta1 to 4.1.0~beta2
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta3 to 4.1.0~rc1
Updated by François ARMAND almost 8 years ago
- Target version changed from 4.1.0~rc1 to 4.2.0~beta1
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.2.0~beta1 to 4.2.0~beta2
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~beta2 to 4.2.0~beta3
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~beta3 to 4.2.0~rc1
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~rc1 to 4.2.0~rc2
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~rc2 to 4.2.0
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.0 to 4.2.1
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.1 to 4.2.2
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.2 to 4.2.3
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.3 to 4.2.4
Updated by Benoît PECCATTE almost 7 years ago
- Target version changed from 4.2.4 to Ideas (not version specific)
Updated by Benoît PECCATTE almost 7 years ago
- Target version changed from Ideas (not version specific) to 4.3.0~rc1
Updated by Benoît PECCATTE almost 7 years ago
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
Updated by Benoît PECCATTE almost 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1246
Updated by Rudder Quality Assistant almost 7 years ago
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.3.0~rc1 to 4.3.0~rc2
Updated by Benoît PECCATTE almost 7 years ago
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
Updated by Benoît PECCATTE almost 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|ed4a7fb950f5bceb1032842971ea0c2dce756422.
Updated by Vincent MEMBRÉ over 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0~rc2 which was released today.
- 4.3.0~rc2: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by François ARMAND almost 5 years ago
- Related to Bug #16773: Batch of new nodes can overflow rudder server with inventories added
Actions