Project

General

Profile

Actions
Copy link

Bug #22344

closed

Missing reports on package directive for all nodes

Added by Gaëtan De La Chagnasse almost 2 years ago. Updated about 1 year ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
-
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
66
Name check:
To do
Fix check:
To do
Regression:
No

Description

We're using this directive to install a bunch of packages on all nodes :

Packages are installed but the compliance always displays missing reports for all nodes.

Here is an example of a package instruction :

And here is the output of the rudder agent run -I :
@
info packageManagement None bash-completion Presence of package bash-completion in latest available version was correct
info packageManagement None rsync Presence of package rsync in latest available version was correct
info packageManagement None vim Presence of package vim in latest available version was correct
info packageManagement None rudder-agent Presence of package rudder-agent in latest available version was correct
info packageManagement None ntpdate Presence of package ntpdate in latest available version was correct
info packageManagement None unzip Presence of package unzip in latest available version was correct
info packageManagement None htop Presence of package htop in latest available version was correct
info packageManagement None iotop Presence of package iotop in latest available version was correct
info packageManagement None ncdu Presence of package ncdu in latest available version was correct
E| n/a packageManagement Post-modification script bash-completion No post-modification script was set to run
E| n/a packageManagement Post-modification script rsync No post-modification script was set to run
E| n/a packageManagement Post-modification script vim No post-modification script was set to run
E| n/a packageManagement Post-modification script rudder-agent No post-modification script was set to run
E| n/a packageManagement Post-modification script ntpdate No post-modification script was set to run
E| n/a packageManagement Post-modification script unzip No post-modification script was set to run
E| n/a packageManagement Post-modification script htop No post-modification script was set to run
E| n/a packageManagement Post-modification script iotop No post-modification script was set to run
E| n/a packageManagement Post-modification script ncdu No post-modification script was set to run

@

Server is 7.1.10, client same version.

Files

Download all files
clipboard-202302030952-phste.png (44.9 KB) clipboard-202302030952-phste.png Gaëtan De La Chagnasse, 2023-02-03 09:52
clipboard-202302030954-4uh9v.png (36.4 KB) clipboard-202302030954-4uh9v.png Gaëtan De La Chagnasse, 2023-02-03 09:54
clipboard-202302030956-o8xwu.png (25.6 KB) clipboard-202302030956-o8xwu.png Gaëtan De La Chagnasse, 2023-02-03 09:56
Actions
Copy link
 #1

Updated by Alexis Mousset almost 2 years ago

  • Category set to Techniques
Actions
Copy link
 #2

Updated by Benoît PECCATTE almost 2 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • UX impact set to I dislike using that feature
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 76
Actions
Copy link
 #3

Updated by Félix DALLIDET about 1 year ago

  • Status changed from New to Rejected
  • Priority changed from 76 to 66
I was unable to reproduce in 7.3 and 8.0 versions which are now the only maintained versions, and so, will close the ticket.
If after upgrading the rudder server the reports are still missing, please feel free to re-open the ticket and add the following info:
  • impacted agent OS
  • rudder-agent version
  • an export of the directive made from the API:
    curl --silent --insecure --header "X-API-Token: $(cat /var/rudder/run/api-token)" --request GET https://localhost/rudder/api/latest/directives/<directive id of the faulty directive>
Actions
Copy link

Also available in: Atom PDF