I enabled the repository and deleted the cache via rm
/var/rudder/cfengine-community/state/packages*. I ran a
rudder agent run and still have a
How can I investigate this problem? Can I open the cache files to check which version rudder considers the latest?
@binibitobi_gitlab If you really want to see what the agent is seeing (outside of cache), you can call the packages api yourself. For instance try to run on your agent:
/var/rudder/cfengine-community/modules/packages/yum list-installed < /dev/null | grep -A3 burp
This will give you the installed version seen by the API, without any cache involved. If you want to see which packages are available for update via the api try:
/var/rudder/cfengine-community/modules/packages/yum list-updates < /dev/null
@ncharles Following your remark on the difference between the burp and burp-client packages, I checked my directive and I test the presence of the burp package and not burp-client. I added a directive for the burp-client package and there the feedback on rudder is OK.
However, on my other servers (Debian), rudder returns "OK" for the directive with the burp package.
Why doesn't it show me 'non-compliant' like the server under CentOS?
In Centos and under Debian, the package is called burp-client. My directive tested the burp package and therefore had a 'non-compliant' coherent return for my CentOS server.
For cons, I do not understand why rudder showed me a return 'compliant' for my Debian servers with the burp packet directive.
apt install vim, but
yum install vim-enhanced