User story #15220
closed
Add a GM to ensure that a kernel module is enable at boot
Added by Félix DALLIDET over 5 years ago.
Updated over 2 years ago.
Description
This will assume that we are dealing with modules loaded via /etc/modprobe.d/ since we can not know what modules are loaded at boot time as drivers or via services.
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/1015
- Status changed from Pending technical review to Pending release
This does not work and journald shows:
Sep 11 13:54:16 agent1 systemd-modules-load[201]: libkmod: ERROR ../libkmod/libkmod-config.c:635 kmod_config_parse: /etc/modprobe.d/enabled_by_rudder.conf line 1: ignoring bad line starting with '(module name)'
The generic method should either edit /etc/modules
and ensure the module name is there, or for systemd
enabled systems, you can create a xxx.conf
file in /etc/modules-load.d/
So, we will only support systemd enabled distribution for now with that generic method.
For reference, for older distribution:
- debian8 and below: edit /etc/modules
, one module name per line
- on sles11: edit /etc/sysconfig/kernel
, look for variable named: MODULES_LOADED_ON_BOOT="module1,module2,etc"
(add the module name here)- centos/red hat 6 and below (not kidding): create a executable file /etc/sysconfig/modules/the_module.modules
with content
#!/bin/sh
/sbin/insmod the_module
- Related to Bug #15691: kernel module loaded at boot GM does not work on non-systemd os added
- Fix check changed from To do to Error - Blocking
- Fix check changed from Error - Blocking to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.13 which was released today.
- Project changed from 41 to Rudder
- Category changed from Generic methods to Generic methods
Also available in: Atom
PDF