Closed foxxx0 closed 3 years ago
Hi,
Short solution would be to check for the OS in your Puppet code and avoid declaring the resources you know will not converge.
Longer option would be to port kmod::load
to a proper Ruby type and provider using Augeasproviders and a way to detect dynamic modules as described by you. That's quite a bit of work though, but you can contact me on my email address if you'd be interested in financing such a development.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi,
we've recently deployed a certain set of generic modules to be always loaded using
kmod::load
. Due to the very heterogenous infrastructure we have unfortunately stumbled upon some issues.Example with Ubuntu 16.04:
These modules are directly built into the kernel, which can be verified by e.g.:
and thus will not show up in
/proc/modules
:These false-positive notices are messy and should be avoided.
Unfortunately consulting
/boot/config-$(uname -r)
is not straight forward, as the desired kernel module specified forkmod::load
needs to be translated/looked-up to its corresponding kernelCONFIG_???
setting.It would be great if you could take a look at this and come up with a fix.