Bug #2443
closed
Policy Server UUID in /var/rudder/tmp
Added by Vincent MEMBRÉ over 12 years ago.
Updated almost 10 years ago.
Category:
System techniques
Description
Information about policy server UUID is located in /var/rudder/tmp/uuid.txt
That directory is shared beetween every agents running, but the information may be different for each of them.
and last running agent will overwrote that file.
That file may be better located in the agent specific directory (/var/rudder/agent-name) to solve that problem.
- Target version changed from 2.4.0~alpha7 to Ideas (not version specific)
- Assignee deleted (
Jonathan CLARKE)
- Assignee set to Matthieu CERDA
- Priority changed from N/A to 5 (lowest)
Matthieu, could you do this modification ?
- Assignee changed from Matthieu CERDA to Nicolas CHARLES
I don't understand what change is needed here. What is meant by "agent-name"? What string should this be, and where do we read it from?
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
This file contains the policy server uuid, for the inventory
However, if you have several agent on the system (like enterprise and community), and each one as a different policy server (which is possible with the current set of promises), the value will be erases by the last agent running, hence an invalid value fro the policy server uuid will be the inventory
agent-name could be community on community edition, and enterprise on enterprise edition
- Assignee deleted (
Jonathan CLARKE)
OK, I understand. This would be nice to have, but I see no urgency here. De-assigning.
- Status changed from New to Pending technical review
- Assignee set to Nicolas CHARLES
- Target version changed from Ideas (not version specific) to 3.0.0~beta2
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/608
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:7ddc31a3d2d524718a007fa9abca30dfccee74e2.
Applied in changeset policy-templates:commit:21c7da7f25727f32383a38c864b8c2d00aa2abde.
Ha, this cause a problem with fusioninventory
Fusioninventory looks for the policy server uuid in /var/rudder/tmp/uuid.txt, but now the file is in ${sys.workdir}/rudder-server-uuid.txt, so the inventory doesn't work as expected
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta2, which were these days.
- Related to Bug #8045: Using Rudder server 3.x + rudder agent 2.11.x, a node doesn't properly detect its change of relay server added
Also available in: Atom
PDF