User story #15220: Add a GM to ensure that a kernel module is enable at boot - Rudder - Issue Tracker

Actions

Copy link

User story #15220

closed

Add a GM to ensure that a kernel module is enable at boot

Added by Félix DALLIDET almost 5 years ago. Updated almost 2 years ago.

Status:

Released

Priority:

N/A

Assignee:

Alexis Mousset

Category:

Generic methods

Target version:

5.0.13

Pull Request:

https://github.com/Normation/ncf/pull...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

To do

Fix check:

Checked

Regression:

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.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Félix DALLIDET almost 5 years ago

Status changed from New to In progress
Assignee set to Félix DALLIDET

Actions

Copy link

Updated by Félix DALLIDET almost 5 years ago

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

PR https://github.com/Normation/ncf/pull/1015

Actions

Copy link

Updated by Félix DALLIDET over 4 years ago

Status changed from Pending technical review to Pending release

Applied in changeset commit:02c0856e1b11277fa3933fcb6b26ab0c8730a646.

Actions

Copy link

Updated by François ARMAND over 4 years ago

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)'

Actions

Copy link

Updated by François ARMAND over 4 years ago

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/

Actions

Copy link

Updated by François ARMAND over 4 years ago

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