Here in Grenoble, back to business with a technical question about Oracle Linux 8.x : I see that the yum package manager is using python (and more specifically a wrapper to detect python2 or 3) and it's failing on my host. Obviously, this comes from python{2 or 3} is not installed by default. After a quick "dnf module install python36", my directives are running nicely. Do you think it could be worth mentioning it somewhere in the doc, or is Oracle Linux considered too a-side (not strictly supported) to bother?
@necar_gitlab yes, it would definitively make sense. Could you open a ticket on the bugtracker? that would be great
Hello @ncharles . Here it is : https://issues.rudder.io/issues/19904
I have one more question :D
Each generic method has result condition, and there are 3 different cases:
success
repaired
error
After i run the agent, I can see 3 different "reports":
compliant
n/a - not applicable
error
repaired
Is there any connection between these reports? I guess that repaired is when the task is done, compliant is when "state" is equal to desired one, error is self-explanatory?
Variable string from command that will probably do what you want
Hello guys !
I wonder, are there any defined variables in rudder server, that can be used in technique-s?
e.g. Every node has defined Hostname, Node_ID. So can I create technique, that as parameter uses e.g. $(hostname) and on execution for each node it will use hostname or Node_ID defined on Node summary page?
I know how to define parameter in technique, and then declare it in Directive, but insted of declearing I want to forward that "global variable" defined for each node.
@ncharles I've question about adding aditional sources to APT repository.
Let's say I want to install Docker or some random package, in order to do that I have to complete 2 steps:
1) Get and add repository GPG key
2) Add repository to /etc/apt/sources.list.d/
And on the next update, I can install the package.
In rudder, I saw two built-in directives:
1) Directive Package repository keys (RPM/APT)
2) Package sources and settings (APT)
The second directive is clear to use, all I have to definre URL of repository, pick distribution and ETC.
But the first one is kind a tricky.
I choose to import GPG key, and then there is field "Long hash of the GPG Key". I tought this would be similar directive to the first one, define url of the key, and add it to the trusted.gpg directory.
But it doesn't work like that.
It seems to me that I've to manually download the gpg key on the node, then add it to the trusted.gpg directory using output of command "gpg --list-keys --keyid-format=long". When I try that command I get no output.
So what am I doing wrong here, is there any other way to manage repository GPG keys? Thanks in advance :)