[fuel-bootstrap] --include-kernel-module & --blacklist-kernel-module are not working
Bug #1526240 reported by
Dmitry Kalashnik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
High
|
Aleksey Zvyagintsev |
Bug Description
Steps to reproduce:
1. Build and activate bootstrap image:
fuel-bootstrap build --ubuntu-release trusty --include-
2. Reboot any slave
3. SSH to slave with new bootstrap
4. Check lsmod | grep core & grep -r fuse /etc/modprobe.
Expected result:
4. core is loaded and fuse is blacklisted
Actual result:
4. core is not loaded and fuse is not blacklisted
tags: | added: team-telco |
To post a comment you must log in.
Modification modules loading\unloading its tricky operation.
By default - each firmware package contain some postinstall scriptf wich perform:
1) Correct adding modules requirements in modprobe.d
2) Perform adding initrams modules and hooks
3) Perform rebuilding initramfs.
All this steps totally depends on firmware maintainer and we cant support all possible situations.
Conclusion: kernel- module & --blacklist- kernel- module will be remove from fuel-bootstrap tool scope
1) --include-
2) User still can add any customization to modules(by they own risk) with --script ${script} parameter
For example:
##
$ cat script
#!/bin/bash
echo "Adding user modification into bootstrap!" d/user_ custom. conf d/user_ custom. conf
echo '# add custom blacklist module, by bootstrap maintainer' >> /etc/modprobe.
echo "blacklist fuse" >> /etc/modprobe.
##