Bug #7638
closed
Rudder agent connect at each runs to its policy server to get its server uuid
Added by Nicolas CHARLES almost 9 years ago.
Updated over 8 years ago.
Category:
System techniques
Description
At each run, the inventory part of the policies execute a curl to the policy server, to get the policy server uuid
this is really not clever, as:
- we do the inventory only during the night, or when the force_inventory class is defined
- it used bandwith
we could at least get the uuid only when it is inventory time or force_inventory as been sent
- Target version changed from 2.11.18 to 2.11.19
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/932
- Status changed from Pending technical review to In progress
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.21, 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
Also available in: Atom
PDF