Bug #21033
openMissing report (though working fine)
Description
Hello,
3 years ago, I have created a custom technique that :- Removes old /var/rudder/cfengine-community/state/packages_updates_*
- Updates /etc/yum.repos.d/rudder.repo, setting its content accordingly
- Ensures that the rudder-agent package is installed and as the latest version
You'll find below its json description [1]. Don't mind the /etc/yum.repos.d/rudder.repo labels, they're not relevant nor troublesome.
I'm using this technique in a directive and in a rule that I usually keep disabled. From times to times, I'm enabling it to update the rudder-agent packages of around 20 nodes, and it has worked nicely for 3 years.
Yesterday, I upgraded the hub from 7.0.2 to 7.1, and with this rule enabled, the part which ensures the rudder-agent package is showing "Missing report".
Here's what I tried :- Disable then re-enable the rule
- On the node, run rudder agent run -ui , then rudder agent inventory. I haven't noticed anything weird.
- reboot the node
- regenerate the policies
- reboot the hub
- wait patiently
So far, no change. On the node, the rudder-agent package is at the same version as the content of Normation's repo, so it's OK.
The only thing is that the report is not done
[1]
{
"type": "ncf_technique",
"version": "3.0",
"data": {
"id": "sit___upgrade_rudder_agent__redhat_like_",
"version": "1.0",
"name": "sit - upgrade rudder agent (redhat like)",
"description": "",
"category": "ncf_techniques",
"parameter": [],
"calls": [
{
"component": "Command execution",
"id": "1fccb96f-b0ee-456f-8876-05640b450a43",
"method": "command_execution",
"condition": "",
"parameters": [
{
"name": "command",
"value": "rm -f /var/rudder/cfengine-community/state/packages_updates_*"
}
],
"disableReporting": false
},
{
"component": "File content",
"id": "994312f3-2760-44e8-84e8-22d570ed1a89",
"method": "file_content",
"condition": "",
"parameters": [
{
"name": "path",
"value": "/etc/yum.repos.d/rudder.repo"
},
{
"name": "lines",
"value": "[Rudder_6.2]\nname=Rudder 6.2\nbaseurl=http://repository.rudder.io/rpm/latest/RHEL_$releasever/\ngpgcheck=1\ngpgkey=https://repository.rudder.io/rpm/rudder_rpm_key.pub"
},
{
"name": "enforce",
"value": "true"
}
],
"disableReporting": false
},
{
"component": "Package state",
"id": "26e6ea8e-5d3c-475d-884e-7793fbf8fd61",
"method": "package_state",
"condition": "",
"parameters": [
{
"name": "name",
"value": "rudder-agent"
},
{
"name": "version",
"value": "latest"
},
{
"name": "architecture",
"value": ""
},
{
"name": "provider",
"value": ""
},
{
"name": "state",
"value": ""
}
],
"disableReporting": false
}
],
"resources": []
}
}
Updated by François ARMAND about 3 years ago
Thanks for reporting, we have changed something in reporting for command exec, which should now be better (and not missing). We will try to reproduce.
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 7.1.1 to 7.1.2
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 7.1.2 to 7.1.3
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 7.1.3 to 7.1.4
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 7.1.4 to 7.1.5
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 7.1.5 to 7.1.6
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 7.1.6 to 7.1.7
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.1.7 to 7.1.8
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.1.8 to 7.1.9
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.1.9 to 7.1.10
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.1.10 to 1016
Updated by Alexis Mousset over 2 years ago
- Target version changed from 1016 to 7.2.5
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.2.5 to 7.2.6
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.2.6 to 7.2.7
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.2.7 to 7.2.8
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.2.8 to 7.2.9
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.9 to 7.2.10
Updated by Alexis Mousset almost 2 years ago
- Target version changed from 7.2.10 to 7.2.11
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.11 to 1046
Updated by Alexis Mousset over 1 year ago
- Target version changed from 1046 to 7.3.8
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.3.8 to 7.3.9
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.3.9 to 7.3.10
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.3.10 to 7.3.11
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.3.11 to 7.3.12
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.3.12 to 7.3.13
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.3.13 to 7.3.14
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.14 to 7.3.15
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.15 to 7.3.16
Updated by Vincent MEMBRÉ 12 months ago
- Target version changed from 7.3.16 to 7.3.17
Updated by Nicolas Ecarnot 7 days ago
- Regression set to No
Hello François,
Now in 8.2.7, I'm witnessing the same issue, but this time, I can read 'Missing report' on a simple "directory_present" method.
The yaml code looks like this :
id: sit___dconf
name: sit - dconf
version: '1.0'
category: ncf_techniques
params:
- id: 5d677175-c3c4-400f-90c7-1543e5975456
name: param_filename
description: param_filename
constraints:
allow_empty: false
- id: ccc158a3-65c7-493f-b273-ae09549df5a2
name: param_keyname
description: param_keyname
constraints:
allow_empty: false
- id: 5f27455c-83ba-424e-a200-fc886d516a35
name: param_keycontent
description: param_keycontent
constraints:
allow_empty: false
items:
- id: 736f37cd-829d-437a-8ea7-d4bad8f63673
name: ''
method: directory_present
params:
path: /etc/dconf/db/local.d
The directory is correctly created and managed, so there is no actual error. Though, the report seems to be missing somewhere.
What can I look for to further debug this issue?
Thank you.
Nicolas