Actions
Bug #3854
closedThe first inventory made display disturbing error messages about CPU
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The first inventory made can't retrieve informations about CPU since the tools to get them is not already downloaded from Rudder server. Nevertheless, the system Techniques will try to use them and will display errors:
[root@centos-5-64 ~]# /var/rudder/cfengine-community/bin/cf-agent [...] I: Comment: Generating file with CPUID information R: @@Inventory@@result_error@@inventory-all@@inventory-all@@00@@inventory@@None@@2013-08-20 10:48:16+02:00##6e3e89a8-14ae-4da8-9ad0-ed76b4819def@#Could not generate the cpuid Proposed executable file "/var/rudder/tools/cpuid-linux-V1.0.sh" doesn't exist /var/rudder/tools/cpuid-linux-V1.0.sh promises to be executable but isn't I: Made in version 'not specified' of '/var/rudder/cfengine-community/inputs/inventory/1.0/fusionAgent.cf' near line 247 I: Comment: Generating file with CPUID information Proposed executable file "/var/rudder/tools/cpuid-linux-V1.0.sh" doesn't exist /var/rudder/tools/cpuid-linux-V1.0.sh promises to be executable but isn't I: Made in version 'not specified' of '/var/rudder/cfengine-community/inputs/inventory/1.0/fusionAgent.cf' near line 247 I: Comment: Generating file with CPUID information Could not read file /var/rudder/tmp/cpuid.arc !!! System reports error for fopen: "No such file or directory" I: Made in version 'not specified' of '/var/rudder/cfengine-community/inputs/inventory/1.0/fusionAgent.cf' near line 438 I: Comment: Adding the CPUID data in the inventory file [...] R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@00@@common@@EndRun@@2013-08-20 10:48:16+02:00##6e3e89a8-14ae-4da8-9ad0-ed76b4819def@#End execution
This should not happen and is disturbing.
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.8 to 2.4.9
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.9 to 2.4.10
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.10 to 2.4.11
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.11 to 2.4.12
Updated by Jonathan CLARKE about 11 years ago
- Status changed from New to 8
- Assignee set to Matthieu CERDA
- Priority changed from 2 to 1 (highest)
Matthieu, please investigate this. It could prove to just be scary, or be the symptom of a worse problem - we must fix this ASAP.
Updated by Matthieu CERDA about 11 years ago
- Status changed from 8 to In progress
Updated by Matthieu CERDA about 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/232
PR available.
Updated by Matthieu CERDA about 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:c5ea5feb6aac0a324585f7acdc22493726cefecd.
Updated by Matthieu CERDA about 11 years ago
Applied in changeset commit:d1b54ebaedec4d5de297508d72765ef312b6039e.
Updated by Nicolas PERRON about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.4.12 which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-November/000061.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog24
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 24 to Rudder
- Category set to Techniques
Actions